WinINET API... Yay or Nay?

From: GSM (gsm00_at_hotmail.com)
Date: 08/11/04 

Date: Tue, 10 Aug 2004 17:16:25 -0700

Hi,

A few years ago, I looked into accessing files over the internet (HTTP and
FTP protocols, specifically) using the WinInet API functions. However, after
looking into this for a while (and reading a few horror stories), I
determined that the WinInet API was too unstable and unreliable to use.
Eventually, the project was dropped.

Fast-forward to three years later (now) I need to write an application that
will download files over HTTP and FTP. Is the WinINet API still considered
buggy, or is it pretty reliable?

One difference is that this time around, we will not support Windows 95.
Windows 98 or later will be required. If I remember correctly, a good number
of problems with WinInet occurred on machines running Windows 95...

This brings me to my second question, regarding deployment. The other reason
that using WinInet posed a problem three years ago is that it would have
made the deployment of our app a real nightmare. Because we will only be
supporting Windows 98 (which I believe ships with Internet Explorer 4.0) and
up, would this still be an issue? would we need to redistribute any DLL's
(or anything else) with our app if we went the WinInet route this time
around?

Thanks so much for your help. I appreciate any advice/pointers you can give
or experiences you can share.

Best regards,

GSM

Relevant Pages

  • WinINET API... Yay or Nay?
    ... FTP protocols, specifically) using the WinInet API functions. ... will download files over HTTP and FTP. ... One difference is that this time around, we will not support Windows 95. ...
    (microsoft.public.vb.controls.internet)
  • WinINET API... Yay or Nay?
    ... FTP protocols, specifically) using the WinInet API functions. ... will download files over HTTP and FTP. ... One difference is that this time around, we will not support Windows 95. ...
    (microsoft.public.vb.winapi.networks)