Design advice for handling different protocols sessions in the server.
posted 4 years ago
I am trying to think about plug-ability and maintainability structure for handling sessions in the server side.
I am sure this issue was raised in many places to any services givers.
Session can be of different protocols: HTTP, Webservice, ProtocolX, ProtocolY,...
After the client communicate with the server via protocol the request will be handled via "adapter" or something like that and the rest of the logic will be the same to all protocols(for example authenticate the client against the DB.. etc etc). the communication layer is the only difference.
So of course i thought right away of having session adapters layer and "sessionProtocol interfaces" which will be implemented.
Anyone could provide and designing suggestions to put all this things together or any other suggestions? (known Design pattern for this case would be warmly welcomed as well).