|
|
|
date: Fri, 18 Apr 2008 07:55:55 -0700 (PDT),
group: microsoft.public.inetsdk.programming.urlmonikers
back
Re: determining the last response
On Apr 18, 9:36 pm, "Igor Tandetnik" wrote:
> genius1...@yahoo.co.in wrote:
> > I have been using you PassthroughAPP for finding out all the request &
> > responses.
>
> > I have following queries:--
>
> > 1. Can we find out which respose is the last response? (While fetching
> > a web page multiple requests are made & we get a response for each
> > request. So how do we find out that which one is the last response.)
>
> Not at the APP level. The APP just sees one request at a time, it
> doesn't have the global picture.
>
> WebBrowser control fires DocumentComplete event when the page is fully
> loaded.
>
> > 2. Can we find out the first reuest fired for fetching the web page ?
>
> Again, the APP doesn't know nor care who is making a request or why.
> WebBrowser fires BeforeNavigate2 event when initiating navigation to a
> new page.
> --
> With best wishes,
> Igor Tandetnik
>
> With sufficient thrust, pigs fly just fine. However, this is not
> necessarily a good idea. It is hard to be sure where they are going to
> land, and it could be dangerous sitting under them as they fly
> overhead. -- RFC 1925
Hi Igor,
Thanks for the reply.
I have already tried using DownloadComplete event for finding out the
last response time , but it did not help since I got some reponses
even after the DocumentComplete event is fired.
Then to confirm it I noted down the time stamps for these events ----
Even the time stamp of DocumentComplete event was lower than that of
the last response received in our APP. i.e. DocumentComplete was fired
earlier.
Any idea about why such thing is happening ??
Is there any other way to find out the last response ???
Thanks & awaiting your reply,
Hitesh
date: Mon, 21 Apr 2008 08:03:57 -0700 (PDT)
author: unknown
Re: determining the last response
genius1232@yahoo.co.in wrote:
> I have already tried using DownloadComplete event for finding out the
> last response time , but it did not help since I got some reponses
> even after the DocumentComplete event is fired.
It is possible with modern AJAX applications that issue requests
programmatically with the help of XMLHTTPRequest. With these
applications, there's often no point in time when the page can be said
to be "fully loaded". A script on the page may initiate new requests at
any moment, in response to user actions or simply on timer.
DocumentComplete fires when the HTML of the page itself, and all
dependent resources (e.g. <img src="someURL">) are downloaded. But it
doesn't take into account any requests issued programmatically.
Another possibility is you have a frame or an iframe on your page, and
get DocumentComplete from it. Every frame, as well as the top-level
browser, fires a full complement of events, from BeforeNavigate2 to
DocumentComplete. The first parameter of each event is the WebBrowser
object that fired it. You need to wait for DocumentComplete fired by
top-level browser.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
date: Mon, 21 Apr 2008 12:56:09 -0400
author: Igor Tandetnik
Re: determining the last response
On Apr 21, 9:56 pm, "Igor Tandetnik" wrote:
> genius1...@yahoo.co.in wrote:
> > I have already tried using DownloadComplete event for finding out the
> > last response time , but it did not help since I got some reponses
> > even after the DocumentComplete event is fired.
>
> It is possible with modern AJAX applications that issue requests
> programmatically with the help of XMLHTTPRequest. With these
> applications, there's often no point in time when the page can be said
> to be "fully loaded". A script on the page may initiate new requests at
> any moment, in response to user actions or simply on timer.
>
> DocumentComplete fires when the HTML of the page itself, and all
> dependent resources (e.g. <img src="someURL">) are downloaded. But it
> doesn't take into account any requests issued programmatically.
>
> Another possibility is you have a frame or an iframe on your page, and
> get DocumentComplete from it. Every frame, as well as the top-level
> browser, fires a full complement of events, from BeforeNavigate2 to
> DocumentComplete. The first parameter of each event is the WebBrowser
> object that fired it. You need to wait for DocumentComplete fired by
> top-level browser.
> --
> With best wishes,
> Igor Tandetnik
>
> With sufficient thrust, pigs fly just fine. However, this is not
> necessarily a good idea. It is hard to be sure where they are going to
> land, and it could be dangerous sitting under them as they fly
> overhead. -- RFC 1925
Hello Igor,
Thanks for your reply !!!
With Warm Regards
Hitesh.
date: Wed, 23 Apr 2008 18:15:28 -0700 (PDT)
author: unknown
|
|
