Pascal, I'm not clear on what the issue is or what you're trying to accomplish either. I'm happy to help if I understood the problem better.
Your comment regarding 6!:3 does not surprise me. I assume that's causing the single thread to sleep so it's blocking the event handler. If you need synchronous web sockets, you could roll your own implementation as it's just a layer over sockets & http. On Thu, Feb 13, 2014 at 1:05 PM, Pascal Jasmin <godspiral2...@yahoo.ca>wrote: > The difficulty with websockets is that an application must always return > to an idle state I believe that's similar to sdasync or any other asynchronous implementation on a single thread. If the thread is busy, then it won't be able to process the events until the thread is freed. If you need parallel web sockets, then you will need create something like what I did on https://github.com/joebo/j-fork-server/ ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
