Parallel HttpWebRequest to the same host

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I am sending a time-consuming HttpWebRequest asynchronously and would like
to get the current progress. Obvious solution, it would seem, to set progress
in a session variable and send the second (parallel) HttpWebRequest to obtain
this progress. This does not seem to work for me: the second request returns
response only after the fist (long one) is completed. I have tried to play
with HttpWebRequest .ServicePoint.ConnectionLimit and
HttpWebRequest.ConnectionGroupName, but without any luck. Moreover,
HttpWebRequest.ConnectionGroupName does not seem to have any effect, i.e.
when I set HttpWebRequest.ConnectionGroupName property and then try to read
HttpWebRequest.ServicePoint.ConnectionName it is not changed and still reads
“httpâ€.
Any clues?

Kind regard,
Veronica
 
Veronica said:
Hi,
I am sending a time-consuming HttpWebRequest asynchronously and would
like to get the current progress. Obvious solution, it would seem, to
set progress in a session variable and send the second (parallel)
HttpWebRequest to obtain this progress. This does not seem to work
for me: the second request returns response only after the fist (long
one) is completed. I have tried to play with HttpWebRequest
.ServicePoint.ConnectionLimit and HttpWebRequest.ConnectionGroupName,
but without any luck.
Click to expand...

Hm... that should work. Did you try setting HttpWebRequest.KeepAlive to
false as well? Can you post some code that shows the problem?

Moreover, HttpWebRequest.ConnectionGroupName
does not seem to have any effect, i.e. when I set
HttpWebRequest.ConnectionGroupName property and then try to read
HttpWebRequest.ServicePoint.ConnectionName it is not changed and
still reads “httpâ€. Any clues?
Click to expand...

AFAIK ConnectionGroupName is only relevant in the context of unsafe
authentication sharing.

Cheers,
 
Back
Top