Joakim Erdfelt

I don't like the idea of polluting the client Session with server / servlet specific concepts. Perhaps a new `ServerSession extends Session` for these kinds of things? Since these are...

> #219 also requested `ServletContext` `HttpSession` and for `@OnOpen`, `@OnMessage`, `@OnError` and `@OnClose`. `HttpSession` isn't valid for `@OnMessage` and `@OnError` and `@OnClose` (the HTTP side of things is long gone...

> I was speaking specifically about the initial post in this issue referring to calling ejbs on web socket method calls. Issue #197 would need to be solved for that....

@VGerris HTTP overlaps with WebSocket *only* during the handshake. So that means all behaviors that come from HTTP (be it Authentication, Authorization, Cookies, HttpSession, etc) can only apply during the...

The `ServletContext` exist to handle the world of Servlets. (Filters, various Servlet Listeners, HTTP, Authentication, Cookies, HttpSession, request dispatching, etc..) The HTTP/1.1 upgrade to websocket is the overlap with the...

_I really wish this spec never had Encoders and Decoders._ I've always interpreted the spec as the implementation always having primitive encoders as default implementations. * `java.lang.Boolean` (`boolean`) as TEXT...

In fact, wouldn't it be swell to just have each of the primitive encoders and decoders declared in the websocket API and ask the implementations to use them? That way...

Have you filed this as a bug at Tomcat?

Jetty doesn't add the Primitive decoders to the decoder list on the either the EndpointConfig.decoders or the ServerEndpointConfig.decoders Those are used internally, when nothing else will handle the object.

We would need to be careful about lookup order as well.