I\'m evaluating SignalR for a medium-load web application.
We\'re expecting ~500 msgs / sec, which shouldn\'t be a problem with SignalR.
However, we\'re worried
You could ofcourse use some kind of queing framework but to achive this with minimum effort you can do it like this...
Serverside: http://pastebin.com/tuicQYGq Clientside: http://pastebin.com/a8EbusuG
I am using XSockets.NET that is a realtime communication platform (since 2009) and the controllers in XSockets.NET have state so this is easy to do.
EDIT: Ohh... to test this use two browsers for example chrome and safari, then disconnect one browser... send some messages from the other then reconnect to see the messages appear. You have to use two different browsers on localhost since xsockets will give each browser a unique storage-id.
EDIT: Added Func to the queue so that you can target specific clients even if they are offline. Now only clients matching conditions will get messages if you want to.
Regards Uffe