> What benefits and disadvantages does QT web sockets have over J's native/direct implementation?
I don't think J has a native implementation of websockets - they're a stream-like transport layer built on top of HTTP requests. AFAICT J has web sockets, but not websockets. This is very exciting! Thanks BillLam - can't wait to try this out! -- Ian On Fri, Jan 24, 2014 at 11:10 AM, Pascal Jasmin <[email protected]>wrote: > Looks like J8 is getting a QT web socket implementation > > http://www.jsoftware.com/jwiki/Guides/JqtWebsocket > > > The noticeable changes with the existing socket library is: > There is a built-in event handler. > Communication is done through the wd layer with strings instead of direct > commands. > > Sorry, if this is asked before you were ready to announce: > > What benefits and disadvantages does QT web sockets have over J's > native/direct implementation? > > (I assume a partial answer is compatibility with more platforms?) > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
