I don't think you should and probably can't keep a connection alive in a web page.
The web is a stateless environment you request a page, you get a page, you're done.
I would suggest you can make additional requests as needed inside an IFrame so the outer page is not refreshed but the page in the IFrame can carry on a dialog back and forth with the server using multiple requests.
Hope that helps,
Joe
Alain Perry <[EMAIL PROTECTED]> wrote:
Alain Perry <[EMAIL PROTECTED]> wrote:
Hi list,
This is partly OT, but I thought maybe some of you might at least know
where to find information on the Internet about this.
I am trying to code a little web-based jabber client with Mono. A
jabber library already exists that compiles and runs great with Mono,
so that will greatly simplify it all. Thanks guys !
However, I am looking for some information about the way things work
with ASP.NET.
Actually, the application will use a _javascript_ PUSH method to send
trigger functions in the HTML webpage when a jabber event is received
on the server. This means I need to keep the connection alive. I tried
to do so using
Response.AppendHeader ("Connection", "keep-alive");
Response.AppendHeader ("Keep-Alive", "timeout=16, max=100");
in the Page_Load method of my page. However, when everything in this
method is don e, the connection is still cut, and nothing is processed
anymore. If I add a Thread.Sleep(1000) at the end of Page_Load, then
the function that sends the "
[EMAIL PROTECTED]
http://www.joeaudette.com
http://www.mojoportal.com
Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term'
