Like others have posted already, I think both of our ideas can be good additions for DynAPI.
I'm not sure about how HTTP keep alive works, but when I have my page load in multiple scripts in Mozilla, you can see the status bar showing Mozilla connecting / retrieving each file. So having the page only load one large file sped up the page loading a good deal.
Jesse
Stephen Carroll wrote:
LOL, well it seems like alot of us are on the same thread of thought. I like the idea of not having to hit the server multiple times, but doesn't 'HTTP keep alive' maintain one socket connection for the duration of gifs, src, etc. that are requested from a given HTTP server? This removes the overhead of open/close sockets at the TCP/IP level to a minimum for any given client. I do believe there is a speed increase in that HTTP parsing doesn't have to take place if it can be included in one main file. For library.load, I introduced a delay to allow multiple files to be requested from the HTTP server in my dynapi.asp idea. I also like the idea of never even having to mess with compression altogether, thats inherent of the dynapi.asp behavior.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/[EMAIL PROTECTED]/
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[EMAIL PROTECTED]/
