On Italian Restaurants, Mafia Bosses & Web Sockets (Part 2)

This is the second and final part of 2 parts article, Part 1 is here

The first partĀ focused on the need to create sequential multi queue Task Scheduler to solve the producer/consumer needs of downstream ordered messages on protocols such as Web Sockets.

This part is not going to be long šŸ™‚

  1. Code for the Web Socket Ā Server (on top the scheduler) along with the unit tests is published hereĀ https://github.com/khenidak/WebSocketsServer
  2. In brief:Ā The web socket server is designed to work as a stand alone server with Owin (including self hosting) and to work on top of Service Fabric.
  3. The web server uses “Session Manager” to allow the hosting process to interact with active connected web sockets (such as find a socket, send a message down stream).
  4. The web socket themselves are strong types, for example a Customer socket type, an Order socket type and so on.
  5. The web socket supports, close (async), Abort, and Drain and close (async).

please go through the readme.md for more details and usage samples.


till next time


One thought on “On Italian Restaurants, Mafia Bosses & Web Sockets (Part 2)”

Leave a Reply

Your email address will not be published. Required fields are marked *