>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....

Yeah, I could see that being a problem... :)

>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.

Definitely, not. This would be a bear to implement, and a META Refresh pull would give you a more manageable and scalable refresh.
Of course the simplest is to just ask the user to hit the refresh button from time to time, or when they want to see if something new is there. *s*

>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.

I think you *could* use ASP:

Response.AddHeader("Content-type: multipart/x-mixed-replace;boundary=MyBoundary")

Then send your data using Response.write:

Do While lLinked
  If lNewData() Then
    cNewData = GetRefreshData()
    Response.Write(cNewData)
    Response.Write("--MyBoundary")
  End If
Loop

Response.Write("--MyBoundary--")

I didn't try it, but I can't see why it wouldn't work. But then again that doesn't mean it will. :)

BTW, Mark I just threw this stuff out as an FYI, I agree with Erik that this probably isn't appropriate for what you were asking about.

Best,
Bill