t***@gmail.com
2006-09-21 07:59:55 UTC
Hello,
I'm a newbie to WinInet and am writing a wrapper class to work with
asynchronous mode.
After some research (it seems like WinInet api isn't documented too
well) I have some open questions:
1. When working with WinInet in asynchronous mode, is there a limit (or
recommended limit) to how many concurrent calls I should make to
HttpSendRequest?
2. When calling HttpOpenRequest (in async mode), I pass a custom
context object which I later reference in the "StatusCallBack"
function (status code INTERNET_STATUS_REQUEST_COMPLETE) - is it safe
to assume that the context object manipulation can be done without
taking any thread safety precautions?
3. If a call to HttpSendRequest times-out, what notification will I get
in "StatusCallBack"?
Thanks!
I'm a newbie to WinInet and am writing a wrapper class to work with
asynchronous mode.
After some research (it seems like WinInet api isn't documented too
well) I have some open questions:
1. When working with WinInet in asynchronous mode, is there a limit (or
recommended limit) to how many concurrent calls I should make to
HttpSendRequest?
2. When calling HttpOpenRequest (in async mode), I pass a custom
context object which I later reference in the "StatusCallBack"
function (status code INTERNET_STATUS_REQUEST_COMPLETE) - is it safe
to assume that the context object manipulation can be done without
taking any thread safety precautions?
3. If a call to HttpSendRequest times-out, what notification will I get
in "StatusCallBack"?
Thanks!