Pavell Bucek, Oracle
Websocket 1.0:
Websocket protocol, 2011, two way communication, better resource allocation. uses http then upgraded to websocket then only websocket frames.
Ajax practice long polling has one open connection. Requests are much larger than a small message. Wastes resources.
Websocket frames are very efficient with good size to data ratio.
Annotated and programmatic way to deploy and access web socket endpoints.
Event driven. @onopen, OnMessage, onerror. Also more complicated programmatic api.
Encoders, decoders, cdi, path query params, header interceptors.
Websocket 1.1, aug 2014 in Jdk8
Session.addmessagehandler
Whole and partial subinterfaces.
Some things that might be introduced in java ee 8. Not guaranteed to be there, speculation.
Cdi issues, @requestscope, sessionscope, applicationscope, convesationscope
Httpupgradehandler not covered in cdi scope.
Low level frame support not yet complete. Filers and interceptors too (only change headers).
Whole and partial subinterfaces.
Cdi issues, @requestscope, sessionscope, applicationscope, convesationscope
Httpupgradehandler not covered in cdi scope.
Not a real good presentation. The guy next to me fell asleep. Talked about possible future of websockets.
No comments:
Post a Comment