cd
2004-10-25 21:07:55 UTC
i'm sorry for cross-posting, but i posted this on the internet.client group
last week n didn't see any activity there so i thought i'd give this a shot
:) ...
-----
hello, and thanks for the great service you offer here for msdn
subscribers. i tried inititially to use .nets httpwebrequest but it
wouldnt allow me to set the destination port without also changing the text
of the url so i'm trying this with the winhttp functions.
if i know that i have an amount of time, 56 seconds for example, to
complete a request and receive the response from a web server can i simply
set that value somehow? (in the dwReceiveTimeout param of the
WinHttpSetTimeouts and the others to 0 maybe) or something or do i have to
split up my 56 seconds into pieces for each of the timeout parameters? (10
for dns, 10 to connect, 10 for request, and 26 for the response for
example) if so, are there some guidelines for what the numbers should be?
thanks again
cd
last week n didn't see any activity there so i thought i'd give this a shot
:) ...
-----
hello, and thanks for the great service you offer here for msdn
subscribers. i tried inititially to use .nets httpwebrequest but it
wouldnt allow me to set the destination port without also changing the text
of the url so i'm trying this with the winhttp functions.
if i know that i have an amount of time, 56 seconds for example, to
complete a request and receive the response from a web server can i simply
set that value somehow? (in the dwReceiveTimeout param of the
WinHttpSetTimeouts and the others to 0 maybe) or something or do i have to
split up my 56 seconds into pieces for each of the timeout parameters? (10
for dns, 10 to connect, 10 for request, and 26 for the response for
example) if so, are there some guidelines for what the numbers should be?
thanks again
cd