less is more

I'm thinking now that the classic server architecture might be best. We eliminate the queues and we eliminate the problems. We eliminate the thread pools (except for servicing socketts) and we minimize the overhead per sockett. A smart client then can maintain a pool of idle socketts and a dumb one can just open new ones as needed. We also reduce the number of potential bugs and speed development. And for notifications, a client interested in them can open a sockett to receive them.

The only special requirement in this case is that a smart client pass the same client id on all socketts so that a login token created on one sockett will work on the others.