Consider websockets

[johann-petrak]

This may be a more direct duplex way of interacting in comparison to HTTP/Rest, so it feels more like the pipe-based approach without actually using the brittle pipes for it.

• lower communication overhead
• stateful
• arbitrary subprotocols, including our own simple ones

Resources: https://github.com/facundofarias/awesome-websockets

[johann-petrak]

On the python side:

• https://github.com/crossbario/autobahn-python
• maybe https://github.com/aaugustin/websockets/
• maybe ws4py https://ws4py.readthedocs.io/en/latest/
• ?? https://github.com/noisyboiler/wampy
• if java or a broker acts as the server: https://github.com/websocket-client/websocket-client

On the java side:

• ?? https://github.com/crossbario/autobahn-java

[johann-petrak]

A text oriented protocol that seems to be common over websockets is stomp: http://jmesnil.net/stomp-websocket/doc/

Python:

• https://github.com/jasonrbriggs/stomp.py

Java:

• https://github.com/gim-/java-stomp-ws
• https://github.com/nickebbutt/stomp-websockets-java-client
• see http://palashray.com/example-of-websocketstomp-using-java/