Revision history [back]

click to hide/show revision 1
initial version

What you have is one way at which you an use the legacy method of AdvertiseName. What I would propose is that you issue the following: 1) Every sensor device use the About Feature to advertise presence. 2) Client applications discover the capabilities and have can identify the sensor devices as unique ones based on deviceId field and/or the different interfaces supported (if you have multiple sensors with different capabilities then you should have different interfaces to define the capabilities of the sensor). 3) To pull data 3a) JoinSession to acquire a sessionId 3b) Create a ProxyBusObject to make method calls 3c) Call methods 3d) Disconnect

If the data that you are using is not that frequent (IE once every 3-5 minutes) you may wish to consider using a Sessionless Signal instead of needing to explicitly join and call a BusMethod.

What you have is one way at which you an use the legacy method of AdvertiseName. What I would propose is that you issue the following: following:

1) Every sensor device use the About Feature to advertise presence. presence.

2) Client applications discover the capabilities and have can identify the sensor devices as unique ones based on deviceId field and/or the different interfaces supported (if you have multiple sensors with different capabilities then you should have different interfaces to define the capabilities of the sensor). sensor).

3) To pull data data

3a) JoinSession to acquire a sessionId

3b) Create a ProxyBusObject to make method calls calls

3c) Call methods methods

3d) Disconnect

If the data that you are using is not that frequent (IE once every 3-5 minutes) you may wish to consider using a Sessionless Signal instead of needing to explicitly join and call a BusMethod.