RE: Re: xAP - The Proposed Architecture Explained - the first extensio

["Mark Harrison" <Mark.Harrison@xxxxxxx>]

OK

I'm going to propose the following:

- ASCII
- First two items are Datasource, and Instance
- After the first two, Items MUST go key/value pairs
- ASCII 10 is reserved for separator


The rest are, for the moment, open

Hence a message might be:

Outlook
Mark
Unread count
19
Most recent subject
xAP changes


.... nice and tight?


-----Original Message-----
From: PatrickLidstone [mailto:patrickl@xxxxxxx]
Sent: 14 August 2002 13:51
To: ukha_d@xxxxxxx
Subject: [ukha_d] Re: xAP - The Proposed Architecture Explained - the
first extensio


--- In ukha_d@y..., "Mark Harrison" <Mark.Harrison@e...>
wrote:
> OK - firstly, the idea is that the messages will be in XML, so that
the message structure can be expanded.

Don't do it! XML is fine as a notation to represent the messages but 
the wire format absolutely should not be XML. As I have said before, 
it is not suited for parsing by embedded devices, and is also an 
unnecessary waste of network bandwidth.

Yahoo! Groups Sponsor

For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx 
Subscribe:  ukha_d-subscribe@xxxxxxx 
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx 
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.