Web 2.0 back ground service tend to become unresponsive quite often, thus leading to web2.0 page hanging.
I would like to propose to google that they recorded the statisical reponsive of web 2.0 ajax request made, and that if it detects a longer than average reponse for url request of the same site as in deviates from the norm that it terminates the connection in the background (java core) and re-initials the connection immediately. You would obviiusly have to have diffrent type of reponse for this action depending on http and https request. Look at time to first packet/byte recive from the server. time to reciving first http headers time to reciving body reponse of http time of average download speed time from last byte packet received, take into account the size of the file downloaded so far all with respect to the normal and standard normal deviation. Research into these facts would allow you to determnine the most significate. I would go as far as to say that this should be built into the next java runtime for google browser. I would also like to sugguest that a web2.0 sites request be monitiored for using http for ajax web the site clear say https and that the browser blocks and alerts of a request if it find somthing irregularity.The iregularity depends on the type of the http content requested (mime type, get/post) whether it be an image, or form submit information, extra. --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
