Mark Thomas
Mark Thomas
Currently section 6.2 of the spec says: > Java EE containers are not required to support deployment of websocket endpoints if they are not packaged in a WAR file as...
It depends on what the WebSocket implementation scans. Section 6.2 of the WebSocket spec allows the implementation to limit itself just to the current WAR. As does the Servlet spec...
Fixing #211 in WebSocket 2.1 essentially requires option 1 as WebSocket endpoints may all be added after deployment has completed. I don;t think there is anything left for the WebSocket...
How much of a problem has this turned out to be? I'm wondering if this a problem that needs to be solved. If we do decide to solve it then...
Same here. I don't recall any issues in this area. I'll leave this open a little longer for others to comment but my current intention is to close this as...
Closing based on previous comment. If an issue does emerge, the issue can be re-opened.
When this was originally discussed in the WebSocket EG the concern was that the life cycle of the HTTP session was separate from that of the WebSocket session. What if...
Good point re the client `Session`. I'm still thinking about pros/cons of the approaches you suggest. What I am going to do is use this as the master issue and...
#219 also requested `ServletContext` `HttpSession` and for `@OnOpen`, `@OnMessage`, `@OnError` and `@OnClose`.
#218 was another request for the `HttpSession` along with some discussion on exactly what is exposed (original object, (read-only) copy. #217 was another request for the `ServletContext` And finally, #175...