angelkyriako / chat-dotnet-core Goto Github PK

Assuming an additional property is added to WSConnection (Session: UserAndToken) and adding support for an WSMessage of action="authenticate".

• Find a way to support a Generic WSConnection for the WS middleware, without depending on ChatApp.Model.

• on connect wait for a few seconds and check if the WSConnection has a not null Session property. If it does not, drop the connection*.

• do not drop the connection, just filter the WSConnections to those that have a not null Session at SendMessage.

• Add a WSConnectionId property on the user model. Update the user when they send the 'authenticate' action. Update again when the connection is dropped.

*drop the connection: a retry mechanism should be setup to be done properly:

1. user's token is invalid or does not exist.
2. server sends a warning message (action=unauthorized)
3. server waits for a while and checks session again.
4. If unauthorized: retry by return at 2 X times or drop connections else: its cool, do nothing.