I've been using PCs for 20 years pal. Doesn't explain why the same url in a
web browser appears instantly (it's only a small text file) yet GetResponse
takes 4 seconds - there must be a reason for it, and I assume you don't know
it.
>>I do some peeking at files on the web in my program with code such as:
>>
[quoted text clipped - 10 lines]
>
> Michael
SurfNet - 06 Mar 2006 10:04 GMT
> >>I do some peeking at files on the web in my program with code such as:
> >>
[quoted text clipped - 15 lines]
> takes 4 seconds - there must be a reason for it, and I assume you don't know
> it.
I see to possibilities.
1) There is a high overhead setting up the HTTP connection and the second
time its reused...
2) The immediate code is compiled the first time and the second time its
already present. That might be a side-effect of dotNET.
3) A round-trip to the server is expensive and the second time the cache is
used (not too likely that this is the case).
Of course combinations are possible too...
- Joris
Michael C - 06 Mar 2006 22:00 GMT
> I've been using PCs for 20 years pal. Doesn't explain why the same url in
> a web browser appears instantly (it's only a small text file) yet
> GetResponse takes 4 seconds - there must be a reason for it, and I assume
> you don't know it.
It's called cache my friend.
Michael