Closed codingchili closed 6 years ago
Did some work on clustering
some changes to be made
The destroy(), update() and isValid() methods in Session is very convenient, it would be preferrable to keep them.
Added session handling to the websocket listener for test purposes.
Applied a mapper to the session query results that sets the ClusteredSessionFactory.
Sessions should be optional and not implemented by listeners.
Would it be possible to use this AND a method for writing to requests that isn't limited to request-reply? Should the Request#write method return a future in such cases?
New ClusteredSessionFactory and ClusteredSession imolementing the Session interface. Queryable and writable across the cluster. Closing for now, the API needs to mature for a bit.
This is a part of implementing #58
Distributed services needs a way to obtain an asynchronous handle to a client.
Should it be possible to create a session from a Request? not right now.