On Sep 17, 2009, at 12:54 PM, Maciej Stachowiak wrote:
On Sep 17, 2009, at 12:23 PM, Brady Eidson wrote:
On Sep 17, 2009, at 2:28 AM, Maciej Stachowiak wrote:
Here's what would need to happen to let loads from unload run to
completion:
1) Implement a way to track all entities that start loads during
unload (all owners of ResourceHandles, say).
2) Add a way (perhaps via an abstract base class) for all such
entities to release their ResourceHandle to another owner and then
cancel themselves.
3) Add code after unload finishes to create an object that takes
ownership of all these ResourceHandles, and stays alive until they
all complete their loads (dropping results on the floor).
...
Would you suggest that, as a best practice, the browser gives users
insight into this activity?
I'm not sure what kind of insight you have in mind.
Something like the ubiquitous download manager that all browser have,
or Safari's Activity Monitor that most browsers have some form of that
shows ongoing network activity.
But if took another idea of yours:
We might even want a hard timeout at some large value (like 60
seconds).
Then maybe that wouldn't be nearly as important.
~Brady
Regards,
Maciej
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
