Here's some random ideas:
- The keep-alive option is a good thing (everything goes faster) and
normally does not impose a problem. If you have a problem on the server
because of that (too many threads or too many sockets taken), always
remember that it is the responsibility of the server to control this and not
the client (browser).
- Note that the connection should disconnect by itself after some time. Did
you measure how much time you had to wait? (probably a couple of minutes). I
think it should never be foreever. Maybe you did not realize this timeout
potentially makes this less of a problem. (?)
For Internet Explorer, the keepalivetimeout registry setting is
KeepAliveTimeout under:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings
- If you just want to turn off keep-alive temporarily just to do a test on
your machine, it is possible that you can turn it off in your browser's
options (set it to not use HTTP 1.1) or by modifying a registry key. Or
else, you can try to find a proxy or tcptunnel that could force it off.
- A potential brute-force solution (not sure it is really reliable): I
know that you can control the keep-alive on a request-basis by modifying the
http headers (at least in IE). You can try to use XMLHttpRequest (from
javascript) and force to turn off the keep-alive option by setting HTTP
Headers. That is - after you finished doing your XML query. -- that's on the
client (browser) side - Make many connections to be sure you saturate all
the available connections (something like 2, 3 or 4).
- Make sure you use a keep-alive-friendly proxy (or tcp tunnel) to really
test that the connections are kept alive and that your method really makes
a difference.
- I do not know if we can control the HTTP Headers from within flash - if
you can, try to modify the headers to shutoff the keep-alive option. It
*might* be possible with the recent flash player 8 (raw sockets).
hope this helps,
B.
2006/4/21, Nathanial Thelen [EMAIL PROTECTED]:
Thank you for the idea on that one. I am particularly looking for a
browser
side only solution in this case.
Thanks,
Nate
On 4/21/06 2:57 PM, David Rorex [EMAIL PROTECTED] wrote:
On 4/21/06, Nathanial Thelen [EMAIL PROTECTED] wrote:
I was wondering if anyone out there know how to force a XML connection
closed once the onLoad has happened? The way it works currently is
that
if
the webserver has keep-alives on, the connection to the server stays
open.
I am pretty sure that the browser controls this, but would love to hear
any
ideas on the topic.
Possibly you could use a php file (or whatever server scripting language
you
use ) on the server, which does only 2 simple things:
1. Send a HTTP header that indicates not to use keep-alive. Keep-alive:
no
or something? look up the exact command. This will tell the browser not
to
use that feature.
2. Print out the xml file, which will be received by flash.
-David R
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
--
Nathanial Thelen
Partner
Userplane
LA: 323-938-4401 x203
www.userplane.com
AOL: natethelen
MSN: [EMAIL PROTECTED]
--
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com