On Mar 13, 2008, at 8:50 AM, Artem Ananiev wrote:
I suppose the following order of loading events for a page with a
single frame (please, correct me, if I'm wrong):
page load started
main document load started
title received
icon received
* main document load finished
** resource load started
resource load finished
page load finished
The the FrameLoaderClient functions about the frame (not the ones that
take DocumentLoader*) are what you want. They are all about this
cycle. dispatchDidStartProvisionalLoad is the one that goes first, and
then there are quite a few others, ending with dispatchDidFinishLoad,
dispatchDidFailLoad or dispatchDidFailProvisionalLoad.
OK, I see. Is there any other load process other than provisional?
All loads start provisional.
dispatchWillSendRequest will be called repeatedly with different
URLs when a server does redirection. This is normal. How it should
be handled depends on what API you've devised.
Is there any separate notification about redirection, or this method
is enough?
There is
dispatchDidReceiveServerRedirectForProvisionalLoad for loads of the
main resource of a frame, but dispatchWillSendRequest alone is all
that's needed for arbitrary resource loads.
One more question: is there any method about starting loading of an
external resource? Is it dispatchWillSendRequest?
dispatchDidReceiveResponse?
assignIdentifierToInitialRequest and dispatchWillSendRequest
-- Darin
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo/webkit-dev
