I am trying to wire up an AsyncController so that when a user clicks save on an order on the order page, all users viewing the same order should get a notification that the order has changed. My approach to implement this is to do long polling ajax requests on the order page, however how to make a scalable AsyncController to deal with this is not obvious to me.
So this is what I have so far, the ID is the ID of the order that is signaled as changed or polled for changes.
public class MessageController : AsyncController
{
static readonly ConcurrentDictionary<int, AutoResetEvent> Events = new ConcurrentDictionary<int, AutoResetEvent>();
public ActionResult Signal(int id)
{
AutoResetEvent @event;
if (Events.TryGetValue(id, out @event))
@event.Set();
return Content("Signal");
}
public void WaitAsync(int id)
{
Events.TryAdd(id, new AutoResetEvent(false));
// TODO: This "works", but I should probably not block this thread.
Events[id].WaitOne();
}
public ActionResult WaitCompleted()
{
return Content("WaitCompleted");
}
}
I have had a look at How to do long-polling AJAX requests in ASP.NET MVC? . I am trying to understand all details about this code but as far as I understand this code it is blocking each worker thread in the thread pool which, as far as I understand would eventually lead to thread starvation.
So, how should I implement this in a nice, scalable way? Bear in mind that I do not wish to use any more third party components, I want to get a good understanding of how to implement this scenario properly.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…