[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: IMPORTANT xAP Basic Status and Control
- Subject: Re: IMPORTANT xAP Basic Status and Control
- From: Stuart Booth
- Date: Sun, 19 Oct 2003 21:49:00 +0000
On Thu, 16 Oct 2003 21:04:14 +0100, Stuart Booth
<<a
href="/group/xAP_developer/post?postID=M8hJSMq33tq3O_dUCAb38NDISbfMFZ2fybY7W34VppXxgFiPnPiZnt60PU4k5I-kBJ1pqQGw2-nzVVjqDnbcqw">lists@x...</a>>
wrote:
>6. Compound status example request. You use:
>
>{
>}
>
>So no body content is included. Seems wasteful to force a dummy
>section name in this case. This is the sort of thing I'd just notice
>was missing and be happy about, although I'm not sure if my framework
>demands a minimum of at least one block in the body of the message, or
>if the xAP spec demands this also.
Just discovered that my framework rejects non-heartbeat messages
without a body of any kind!!!
I haven't yet gandered the spec to see what it says on this topic.
S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=GRNcZUTJXKlIXum296R2JYcf8roxwU6l9TRPW6l8rNoVjcuix1a14TuXqmsDpjYl4Y4FUGSu5eD68OyUVQkl1w">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net
<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|