SockJSProxy is a simple proxy server that proxies message from SockJS_ to a
ZeroMQ_ socket and vise-versa.
+Using it you can create real-time web-based application in any backend
-The incomming messages socket is a ``PUSH`` one (by default on port ``9241``), where
+The incomming messages (i.e. sent by the client, usually a browser)
+socket is a ``PUSH`` one (by default on port ``9241``), where
the proxy will push messages to. All messages are 3-part messages in the form of:
-``message_type`` can be one of these. The other arguments are described under each
+``message_type`` can be one of those, listed below. ``session_id`` can be
+used to identify the connection. A reconnect of the
+client will result in a new session id.
Sent when a client connects to the server. The ``session_id`` is set,
-The outgoing socket is a ``PULL`` one (by default on port ``9242``), where the
+The outgoing (for messages you wish to send to the client)
+socket is a ``PULL`` one (by default on port ``9242``), where the
proxy will read messages and forward them to the SockJS client (usually a browser).
The format is like the one for incomming messages:
Send this to forward a message to a client with ``session_id``.
- ``data`` contains the message
(as bytes) for the client.
+ ``data`` contains the message for the client.
Disconnect the client with the given ``session_id``.
``data`` is discarded but *must* be present in the message as
+ Disconnect all connected clients. ``session_id`` and ``data``
+ are discarded, but *must* be present in the message (leaving
+ them empty is a good idea).
--verbose, -v Make the server output more information - useful for
+When the server is running in the foreground - pressing ``Ctrl+C`` would stop it.
+If you use something like ``nohup`` do deamonize it - send it ``SIGTERM``
+(see ``man kill`` for more info) and it will gracefully stop.
+ - Added ``disconnectall`` capability to force all clients
- Switch from ``PUB/SUB`` socket pair to ``PUSH/PULL``.
- Add support to force the client to disconnect.