The protocol shift from text to binary has only a trivial affect on the J server code - it simply means that messages sent back to the client will now be marked "binary" instead of "text".
However, the difference may be important to the client (the browser), or to any application code that has been loaded in with the server. The default onmessage handler (ws_onmessage_jws_) has a simple example of switching behaviour based on protocol. Also, if you are sending JSON messages, then text should be sufficient, but if you want the server to return 3!:1 representations, then the protocol should be binary. On Mon, Jul 24, 2017 at 3:31 PM, Raul Miller <rauldmil...@gmail.com> wrote: > Would it be possible to expand a bit on the scope of protocol shifting? > > (Specifically: if a base mode client requests shifts the protocol to > binary, which requests would be affected?) > > Thanks, > > -- > Raul > > > On Mon, Jul 24, 2017 at 6:17 PM, chris burke <cbu...@jsoftware.com> wrote: > > There is a new addon that provides a J websocket server. See > > code.jsoftware.com/wiki/Addons/net/websocket . > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
