exlted / twostep Goto Github PK

Once we have connections able to be created, we should build the message router which will allow messages to be sent between connections. This should look solely at the routing information on the message packet to determine which connections need to be sent it.

There could be hundreds of messages per second, so this does need to be developed in a performance conscious way.

This will be the primary public interface of Twostep, a connection handler which will keep track of what messages each connected container is requesting to be notified of. We need to be able to establish a websocket connection with any valid request, maintain it, and keep track of what messages they want to be sent.

• Allow connections to be made with the external containers
• Maintain connections with external containers
• Safely drop lost connections with external containers
• Develop API to allow external container to modify its status inside of Twostep

Containers should request to connect to Twostep, not the other way around, think of this as the server, and all "plugins" as the clients.