leonhartley / coerce Goto Github PK

Because networking code is easily switchable in Coerce (Example: it's easy to switch from using Netty to a NIO implementation without having to modify any implementations of the Coerce framework), I have yet to make it so we can alter the pipeline / have multiple codecs (at the moment, you can only have 1 encoder and 1 decoder, the pipeline is unchangeable).

Create a way to map strings to request classes so we can allow for multiple languages to connect to the Coerce Messaging server and use the asynchronous request & response system.

I think a web based console for the Coerce services would be a good idea, with integration with the messaging server lets you manage your authentication tokens, view status, information regarding the clients, the messages they're sending etc.

Coerce Console could be a web application that allows for the management of all Coerce-related services.

At the moment, authentication must be done via individual implementation of the Messaging API, it would be a good idea to implement authentication from within the library via tokens or something.