Re: xAP Schema Questions

[Kevin Hawkins <lists@xxxxxxxxxxxxxxxxx>]

That will be very nice, I look forward to that,

Adding a source name to the subaddress part of the application
address is ideal. It cleanly shows that you have one application serving
several endpoints (each zone).  Yes you will have to create a unique UID
for each zone but only differing in the last two digits for example

UID=FF222200 could be your whole application and is where you should
orginate heartbeats from
UID=FF222201 could be the first zone eg
source=slyfox.jrmc.<servername>:LivingRoom
UID=FF222202 could be the second zone eg
source=slyfox.jrmc.<servername>:BedRoom

Target=slyfox.jrms.<servername>:* would address all your zones as one
Target=slyfox.jrms.<servername> would address the main application
Target=slyfox.jrms.<servername>:> would address everything

Sneak preview... Please in your code make allowances for UID's to be of
varying lengths in xAP (and therefore to be able later in your code to
insert delimiters).  In the next release of the xAP spec we are likley
to increase the length of the UID and probably add delimiters between
the various components   eg UID=FF.2222:01   where each component part
can now be of an increased length. The last component part (currently at
2 digits for the sub address ) is where we are hitting restrictions
currently and is where people need more address space.   THIS IS NOT
CONFIRMED AS THE FINAL AGREED SPEC YET but it is likley to be of this
style.  Hubs will need to be modified to support the new format BTW.

Kevin



harley0922 wrote:

>I am working on a xAP Connector for J River's Media Center(JRMC) and
>need some clarification on a few items.
>
>JRMC has multi-zone capabilities.  I would like to be able to send
>messages that would indicate what zone the data is associated with.
>I
>am thinking that I would append to the source the zone identifier, ie
>slyfox.jrmc.<servername>:zone1.  Is this correct?  Do I need to
>assign
>a different UID to each zone?
>
>
>TIA
>Rick
>
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>