Theres a significant bit of implementation there I dont deem entirely
necessary (the queue part doesnt seem necessary to me) but writing
some kind of async implementation is the only way that will scale at
all and he got that right. I too am implementing with
IHttpAsyncHandler. I dont know much about the async pages in
ASP.NET
2.0, but hypothetically I believe you could fit Comet in there too,
but the async pages seems like it'd be a lot more computation cost /
complexity than you'd need. BeginProcessRequest EndProcessRequest is
cloes to the metal and the right way to go.
The real heart of the work isnt documented in the article. Its all
about your async event itself, the CometAsyncResult. Hope this gets
you on the right path. Good luck.