I have looked a bit at websockets.They are going to be an important new technology (not so new, but slow to be adopted). They add stateful socket connections to the internet (which mostly uses stateless http connections).
I looked at adding them to JHS and decided they added complication without major new benefts to the particular goals of JHS.. Instead of tacking them onto JHS they should be added as part of a new J websocket server. I did cobble together the required J code so that a J server could connect to a websocket request and do the handshake necessary to have a normal socket connection with a web socket client. It was mostly reading the specs and took a few days. With the connection handshake protocol in place, then a J server to websocket clients is exactly the same as a J server to socket clients. This is a very interesting area to be working in. On Tue, Jul 8, 2014 at 9:36 AM, Michael Dykman <[email protected]> wrote: > I have done a fair bit of work with websockets and not-J. A websocket > server needs to be aware of extensions to HTTP that are used to > establish the socket; Unfortunately, our J web server has no such > facility. > > On Tue, Jul 8, 2014 at 8:41 AM, Devon McCormick <[email protected]> wrote: >> Hi - >> >> has anyone done anything with J and websockets? >> >> Thanks, >> >> Devon >> -- >> Devon McCormick, CFA >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm > > > > -- > - michael dykman > - [email protected] > > May the Source be with you. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
