thread_delay blocks all calls to same action about snap-core HOT 2 CLOSED

Sorry, I don't understand this bug report; could you please be more specific about what the behaviour is and how it deviates from your expectations? On my system this program behaves exactly like I expected; calling /blocker from two different curl requests simultaneously works just fine.

I think the issue here is that you're slightly misunderstanding the Snap I/O model; when you issue a "writeBS" you're not actually causing data to be immediately written out of the socket. Instead, you're building an Enumerator that will send the data out when paired with an iteratee consumer later.

To do comet with Snap you'd instead want to build an Enumerator which spooled the data out of the socket; you can't do it from within the body of a handler.

from snap-core.

Okay, so this is my fault, although I still have to do some investigation into browser behavior. I was testing with Chrome and I was never seeing the "before block" being printed until the first request had completed. It is Chrome that is never initiating the request, I verified this with netstat.

Thanks for the info on the streaming comet request. My current needs are not streaming so much as I just need to dangle a connection until an event occurs, so I do not think I will need to delve into that.

from snap-core.