I think those low level functions are not part of websocket spec. Security is already handled by websocket protocol.
Since J is single thread, those globals will not cause any trouble. A handler can erase them if they are no longer used. Anyways, IMO, to compare socket with websocket is analogous to compre an apple with an pineapple. Пн, 10 фев 2014, Pascal Jasmin писал(а): > demos work fine. (and avast makes no complaints about the zip version of J8) > > I notice that sdgetpeername and sdgetsockname do not work on websockets > (understandable if they are not sockets) and there is no QT equivalent for > the functions. > > Is that something not implemented by QT, or not implemented by the J version? > > I can provide use cases, but the most obvious ones are centered around > security and logging, authentication, and tunneling or calling back > disconnected nodes based on IP addresses. > > I notice that wss0_jrx_ , wss1_jrx_ are "global" variables that persist > through connect/disconnect (calls through handler). Perhaps these parameters > could be set to peer/sock name/IP for the onopen event, if a > qtgetpeername/sockname is somehow difficult? > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
