Re: Multiple Message Bodies

[Mal Lansell <mal@xxxxxxxxxxx>]

Multiple bodies are not supported.  One of the core aims of xPL is
simplicity, to enable embedded devices to handle xPL as well.  That
means all messages follow quite a strict format, with one header
followed by one body.

As for repeated field names - they are allowed, and in fact are often
necessary.

For example, the groups and filters that you see in the device
configurations in xPLHalManager are arrays (in this case with 16
elements).  In order to fill in the array, a config message would
contain group= or filter= items as many times as needed (the code will
assume that the first one in the message is array element 0, then
element 1 etc).

I've used the same system in other schemas when specifying a path name
or URL - with multiple path= entries, each containing the next piece of
the path - e.g

path="c:"
path="windows"
path="system32"

The application that parses this kind of message would concatenate the
paths (and add the appropriate separators - '\' for windows).

HTH

Mal







Mark Hindess wrote:

>
> On 11 December 2005 at 9:06, "mustang8760"
<ericvic@xxxxxxx> wrote:
>
> > Can xPL messages have multiple bodies in them? I couldn't find
> > anything in the docs that states one way or another.
>
> I've looked at quite a few of the xPL implementations available for
> linux/unix machines and none of them would support it.  That seems to
me
> like a good indication that it isn't intended.
>
> It would be a good idea to clarify this in the document.
>
> There are other similar issues that would probably benefit from some
> clarification.  For instance, whether developers should be permitted
> to repeated field names - currently there aren't any restrictions on
> developer fields.
>
> For example:
>
>   x10.basic
>   {
>   command=on
>   device=b2
>   command=off
>   }
>
> I suspect some implementations might treat this as 'command=off' even
> though 'command=on' field is in the correct position.
>
> It would probably be a good idea to specify that:
>
>   Field names in the body should not be repeated.  Implementations
>   should use the first value and ignore subsequent values if they
>   receive messages with duplicate fields.
>
> Regards,
> Mark.
>
>
>
>
> xPL Links: http://www.xplproject.org.uk http://www.xplhal.com
> http://www.xpl.myby.co.uk
> To Post a Message: ukha_xpl@xxxxxxx
> To Subscribe:  ukha_xpl-subscribe@xxxxxxx
> To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx
>
>
>
> SPONSORED LINKS
> Protocol analyzer
> <http://groups.yahoo.com/gads?t=ms&k=Protocol+analyzer&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=QulmGKu5OpHgigyaWFXqqA>
> 	Protocol converter
> <http://groups.yahoo.com/gads?t=ms&k=Protocol+converter&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=_Gav_2JNLbgwjsCn8RqM-w>
> 	Sip protocol
> <http://groups.yahoo.com/gads?t=ms&k=Sip+protocol&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=d2G6YVkW-P5WBFmpuWQ3Zw>
>
> Tcp
> <http://groups.yahoo.com/gads?t=ms&k=Tcp&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=9xqmZjMntiOfVEPLIpwKUg>
> 	Protocol analysis
> <http://groups.yahoo.com/gads?t=ms&k=Protocol+analysis&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=j5RxaJ5TSW2NTgWhIna4qQ>
> 	Protocol
> <http://groups.yahoo.com/gads?t=ms&k=Protocol&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=OPnkI6GadMASTgKewyeqDQ>
>
>
>
>
------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
>     *  Visit your group "ukha_xpl
>       <http://groups.yahoo.com/group/ukha_xpl>"
on the web.
>
>     *  To unsubscribe from this group, send an email to:
>        ukha_xpl-unsubscribe@xxxxxxx
>       <mailto:ukha_xpl-unsubscribe@xxxxxxx?subject=Unsubscribe>
>
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
>
------------------------------------------------------------------------
>