Hi Matt,
Thanks for your quick reply.
The cuepoints/metadata solution would not work with us as our information is not sent from our broadcasting computers, and is persistent even when we are not live.
Setting up an HTTP provider is similar to what we already do, so are you suggesting we poll the server for changes (i.e. keep asking the server for the information & spotting when it changes)? That’s rather wasteful when we have 1,000 + connections. The shared objects have a neat solution, they know who is connected, so when they update, they send a message to just those people connected. No unnecessary checking to see if something has changed. If we poll the server, we may have 1000+ unnecessary messages every 5 seconds.
We are looking for a way to avoid this - have I understood your solution properly? Is this what you meant?
As people move towards HTML5 solutions, something that updates clients like shared objects do - but without Flash (God bless it) - will be welcome.
ys,
Antardwip das