I have to agree with Sanjay on this.
I use conventional polling based on a client-side timer of 15 seconds in
my CAD/Situation-Awareness application, with the server responding
immediately. (This is after a long and hard look at alternatives.)
Simplicity itself, and readily tested and tweaked as necessary.
My concern with Comet/BOSH/etc. was re testing; I'm not alone among
developers in not having a realistic operational environment as a test
bed, so simplicity and ready visibility into the app's operation is key,
IMO. Those packages, despite their merits, represent another black box
that might defy comprehension.
Websockets has the potential to change my thinking, however, once it
reaches some level of maturity. It seems to represent a clean approach
to the problem, with apparently direct visibility into its operation.
AS
On 5/23/2011 2:55 AM, Sanjay Bhangar wrote:
hey,
I have some experience building a "real-time collaborative" app -<big snip>
_______________________________________________
Users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/openlayers-users
