>>FWIW, every implementation I have ever seen of "push" technology, is not push technology at all, but timed or coordinated pull using a meta refresh tag, HTML+ time, ActiveX, or Java to execute the request.
>>
>>True "Push", AFAIK, does not exist with HTTP.
>
>Hi Erik, Ronald, et. al
>PFMJI,
>
>Its been a while since I looked at this, but there is a MIME type that allows server push via a CGI (and I am guessing ASP) script.
>
>The MIME type is multipart/x-mixed-replace
>
>How it works is you send the page with this in the header (HTTP header, server side) and a Programmer-defined boundary string, and it keeps the pipe open. Then your script can periodically send refresh data, followed by the boundary string, until the pipe is closed.
>
>Its true push, but its (was, I haven't looked at this in about 3.5 years) a little tricky to implement, and the server needs to be set up to handle it.
>
>I read about it in CGI Programming on the World Wide Web (Nutshell Handbook)
>by Shishir Gundavaram
>http://www.oreilly.com/openbook/cgi/
>(the book is out of print, but is online at this link)
>
>I also found this link, but the above is probably better:
>http://docs.rinet.ru:8083/WebPub/ch26.htm
>
>HTH,
>Bill


Cool. I had never heard of this. FWIW, I did a little research on my own, and found a pretty good explanation at http://home.netscape.com/assist/net_sites/pushpull.html.

For a busy sight, I would be very wary of the practice of keeping a port open and dedicated to one client for an indefinite amount of time....

Mark- I don't this technology is what you want to use to address your original question. FWIW, the "x" in x-mixed-replace stands for experimental. But it looks like this MIME type hs been supported for a while now.
The common MS web server tools out there don't directly support this MIME type, and AFAIK, you'd have to write your logic in Perl or another CGI language.