The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: <ukha_d@xxxxxxx>
  • Subject: RE: Re: xAP - The Proposed Architecture Explained - the first extensio
  • From: "Mark Harrison" <Mark.Harrison@xxxxxxx>
  • Date: Wed, 14 Aug 2002 14:21:00 +0100
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@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
{short
description of image}

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.

Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.