Hi Enrico, I went through the proposed mechanism of notifications based on WebSocket protocol. I think this mechanism has the additional overhead of server needing to keep the connection alive for all the clients which need notification. This works well if the number of clients are less. In case of scenarios where the clients are more, then the server needs to manage a lot of connections.
The additonal drawback of this mechanism is that if there is no change in the map data then the connections still needs to be managed by the server. -Ravi ________________________________________ From: [email protected] [[email protected]] on behalf of Enrico Marocco [[email protected]] Sent: Monday, July 16, 2012 1:09 PM To: [email protected] Subject: [alto] WebSocket-based notifications Folks, Jan and I have just submitted a draft proposing a server-to-client notification mechanism based on the WebSocket protocol: http://tools.ietf.org/html/draft-marocco-alto-ws-01 The mechanism proposed is one of the several possible, and the draft at this point delineates the idea only at quite a high level, without delving too deep into the details. Yet it should be enough to start a focused discussion, so please, if you are interested in the topic, take a quick read and share your thoughts on the list -- whether you feel this is a promising way to go, or if you have alternatives that you think would fit better. -- Ciao, Enrico _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
