Hello,
I wanted to give you an update on the ETSI Standardisation of RadioVIS.
The work has been going on throughout the summer, with a smaller group of people intensively editing the document, and meeting face to face to resolve integration issues.
Progress has been good, and we expect to have a final version of TS 101 499 (Visual Slideshow) to share shortly, which will go to ETSI.
STOMP Protocol - Update
I wanted to give you advance warning of a change in the specification. The STOMP protocol has always been a core signalling protocol for RadioVIS, and will remain so. The STOMP specification includes functionality called 'receipt', which allows a server to confirm that a client has successfully subscribed to a topic. This functionality exists, but has not been defined within RadioVIS.
In Visual Slideshow, the receipt functionality becomes mandatory for the server. If a server does not confirm subscription to a topic within 10s, the client must assume a failure, and stop trying to use IP, even if it exists with a _radiovis._tcp. SRV record. This is to allow devices to 'fallback' to using content from broadcast channels if there is a failure (intended or unintended) on the IP service.
If you are using a reference STOMP server (ActiveMQ, RabbitMQ etc.), receipt is already supported, and you probably won't need to do anything.
If you have written your own STOMP server, you should plan to update it by the end of 2014 to support the receipt functionality. If you don't, devices confirming to the updated specification won't be able to use your RadioVIS services (images or text) any more.
You're welcome to post questions about this change to this group.
Nick