0

I've been looking for IIS based solutions for comet/push/reverse-ajax pages, and came upon asynchronous controllers

It seems like that allows xhr long polling without the problem of running out of threads, am I correct? Does this allow fairly decent scaling for long polling pages?

carpat
  • 861
  • 10
  • 25
  • Scalability is a quite a complex concept. You cannot say it is scalable while you don't build it and test it. – Oybek Feb 01 '12 at 15:38
  • 1
    Develop a project, carry out a stress test, then optimize, then stress test, then optimize, then stress test... – Oybek Feb 01 '12 at 15:39
  • There are inherent scalability problems that can be solved before testing / optimization. I know that with a plain long poll request, each client using a page will use a thread, and that puts a low cap on the number of clients that can be connected. Asynchronous controllers will theoretically get rid of that particular constraint - however I see a lot of questions on here about IIS / ASP comet implementations, and no one has suggested using async controllers as a solution (that I've seen), which makes me wonder if there is something I'm missing. – carpat Feb 01 '12 at 15:49

3 Answers3

2

If you are looking for a pro solution with built in websocket, pick PokeIn

Patrick Cooper
  • 71
  • 3
2

I would say take a look at signalR. Nodejs for iis is also an option

adt
  • 4,320
  • 5
  • 35
  • 54
0

See ASP.NET MVC 3 real time events.

To make scaling easier/less of an issue I'd recommend using a dedicated realtime server (see this realtime technology guide; something that has been built from the ground up with realtime communication in mind.

Community
  • 1
  • 1
leggetter
  • 15,248
  • 1
  • 55
  • 61