Response.IsClientConnected

[alien2_51]

I need to know if the client is connected from the session_end, how can I do
this.....

[alien2_51]

"Scott M." <s-***@badspamsnet.net> wrote in message
news:eX**************@TK2MSFTNGP10.phx.gbl...

Session_End fires when the session is no longer valid
Sorry.. That's not true.. Session_End fires when the timeout has been
exceeded....
The session is still valid in the Session_End... I have full access to all
session vars inside the end event..

so you would never have a connected client at that point.

Try:

If Response.IsClientConnected Then
your code here
End If

But put this code into an event prior to Session_End.
Be specific please... What event fires before Session_End...?

Also, please do not cross-post as you have done with this message.
I made 1 post to many newsgroups... Whats wrong with that....?


"alien2_51" <da********@n.o.s.p.a.m.monacocoach.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

I need to know if the client is connected from the session_end, how can

I do

this.....

[Alan]

> > Also, please do not cross-post as you have done with this message.

I made 1 post to many newsgroups... Whats wrong with that....?

It's generally considered bad 'netiquette' to post a single message to
multiple groups - especially when the groups chosen (dotnet and classic ASP)
have little in common.
http://www.my-newsgroups.com/SiteMap/netiquette.htm

Alan

[William Tasso]

Alan wrote:

Also, please do not cross-post as you have done with this message.
I made 1 post to many newsgroups... Whats wrong with that....?

It's generally considered bad 'netiquette' to post a single message to
multiple groups

generally - sorry we have to disagree.
especially when the groups chosen (dotnet and
classic ASP) have little in common.

however, we do agree in that particular instance ;o)

multi-posting OTOH is always irritating for well documented reasons

--
William Tasso - http://WilliamTasso.com

[Adrian Forbes - MVP]

> I need to know if the client is connected from the

session_end, how can I do this.....

Use this handy routine in your session_onend;

bClientConnected = False

Now if you want to know if the client is connected in your
session_onend simply query the value of "bClientConnected".

The only time the client is "connected" to your server is
when they are physically receiving a response which is why
you would use Response.IsClientConnected inside a normal
ASP page. If you were writing out 100,000 lines of a
table you might want to check that the data is being
receieved by a browser somewhere.

Beyond the milliseconds that client and server are
connected via TCP/IP, the server has no way of knowing if
the client is still looking at their site or if they have
shut the browser or are just looking at other sites.

When the session_onend fires the server is telling you
that it is now assuming that the client has wandered off
and is no longer interested in your site. It can't know
for sure cos HTTP is connectionless, so it makes the best
guess it can and relies on the timeout.