Christian Biesinger wrote:
Daniel Savard wrote:
in the second sample, image2.gif got 2 different ID).
image2.gif will probably not be requested from the server again (it will be found in the imagelib memory cache).
If the request for image2 doesn't go through the network, it is OK for me. But this is only a 'plus' if the two can be seen and can have two different ID.
What is my real need, is to be able to have something really unique for all request that really go through the network and also, be able to tell which request belong to which other request.
For exemple, two request for the same page may return different result even if the URL is the same (SSI, etc). This is the reason I look for a way to uniquely identiry each URL request.
I looked at nsIHTTPChannel, nsIHTTPChannelInternal, nsIRequest, etc and also the owner, loadGroup, observers, etc and I am still not able to find a good way to identify each Request and the page they belong to. Some have a loadGroup, some don't, some have a owner, some don't, etc. And as I said in the first post, some Request object change between onModifyRequest and onExamineResponse! So I can't even track them with the object pointer.
Thanks for the precision, Daniel Savard _______________________________________________ Mozilla-netlib mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-netlib
