Hi,
If I use asynch Wininet is there any purpose in hiving of the Wininet calls
into separate threads and the extra complication which ensues? As from what
I can see the system starts a separate thread implicitly for the asynch
calls anyway.
The reason I ask is I imagine the thread switching might ensure that the UI
remains responsive - plus there may be other issues you can enlighten me
with.
My application is "real-time" and will be applied to a Pocket PC/Smartphone
as well as WinXP so I need the quickest/most efficient functionality
possible.
Also the UI response must be as fast as possible.
The application basically "GET"s a website for info then issues occasional -
through crucial "POST"s prompted by the user via the UI.
Both the GETS and POSTS must be carried out as close to real-time as
possible.
TIA
