[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: xAP and XML
- Subject: RE: xAP and XML
- From: Edward Pearson
- Date: Thu, 18 Mar 2004 21:26:00 +0000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<TITLE>Message</TITLE>
<DIV><SPAN class="051361621-18032004"><FONT
face="Arial" color="#0000ff" size="2">No
sure I follow the logic here. If the wire protocol was different then
low-end devices wouldn't be able to deal with the messages so you'd loose
compatibility. If you need communication between powerful hosts
then you don't need to make the compromises that xAP does to deal
with low-end devices. If you remove these compromises and
move to xml then you have webservices. Or worse, reinvented a poor
relation to webservices. Bur xAP messages delivered in SOAP wrappers - now
that might be useful (eg, across the internet) and very easy with .Net or
Java now they have all the tools to do this built-in. But I can't see the
point of XML xAP on the wire unless it was at the metadata level, say, a
home control application downloading the latest version of a
manufacturers device xAP schema to match its just updated firmware...&
lt;/FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV></DIV>
<DIV class="OutlookMessageHeader" lang="en-us"
dir="ltr" align="left"><FONT
face="Tahoma" size="2">-----Original
Message-----<B>From:</B> Johan Helsingius [mailto:yahoo@xxxxxxx]
<B>Sent:</B> 18 March 2004 20:12<B>To:</B>
xAP_developer@xxxxxxx<B>Subject:</B> RE: [xAP_developer] xAP
and XML</FONT></DIV>
<BLOCKQUOTE class="cite" cite type="cite">
<DL><FONT face="arial" color="#0000ff"
size="2">
<DD>No absolutely not - the message structure on the wire stays
exactly the same. The decision not to use XML on the wire was a conscious
one - if you look at the last example you can see why - it's hopelessly
inefficient in byte terms, and much much more complex than xAP to parse. As
you suggest, the similarities allow programmatic mapping from xml to xap
structures and vice-versa - exposing this to programmers would allow them
the benefit of xml tools on those machines powerful enough to exploit them,
but still allow low end devices to come to the
party.</FONT></DD></DL></BLOCKQUOTE>
<DL></DL>How about a separate "wire protocol" based
on XML for fast IP betweenpowerful hosts? The xAP semantics and
compatibility would remain, whileallowing for compatibility with low-end
devices/networks?<X> </X>Julf
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|