ahhh... that makes sence ("HTTP Keep-Alives" - that rings a bell...)so back to Mark's suggestion of accessing the underlying java to get it to work in CF? oooh, not this little black duck, methinks.... thanx Kym barry.b -----Original Message----- From: Kym Kovan [mailto:[EMAIL PROTECTED] Sent: Thursday, 22 April 2004 10:14 AM To: CFAussie Mailing List Subject: [cfaussie] RE: isClient<still>Connected - aborting cancelled request Hi Barry, >with all my years with ASP I couldn't quite work out how >Response.IsClientConnected worked... > >does it go down into the TCP stack to see if packets are still returning? >does it work off a type of ping? considering we're dealing with a >connectionless protocol, it all seemed like voodoo to me then... With Web pages we are dealing with a stateless protocol but lower down almost every server/browser combo probably has "HTTP Keep-Alives" enabled so the actual TCP/IP connection is still there, just doing nothing. I suspect that asp's IsClientConnected is looking at that keep-alive connection rather than anything else. If the browser goes away then IsClientConnected would know about it. -- Yours, Kym --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
