I didn't see any messages about problems with wininet specifically in a Windows NT service. There were a few about NTLM proxies but I haven't experienced them.
In any case, wininet is for clients only and I don't run it in a service. It is pretty easy to write a client that can use either wininet or straight gsoap. The advantage of wininet is the support for intranet settings and proxies and no need for supplemental config. Not sure what you mean by user messing with the IE settings. IE still works but the wininet plugin doesn't? Perhaps the new proxy or other settings block connections to your soap server? You will need to debug that one yourself. Regards, Brodie --- In [email protected], "Ask Ari" <arigapud...@...> wrote: > > > Thanks for the response. As per some posts - wininet is problematic when run > in a windows service. I presume you don't do that. > > Also, if a user messes up with IE settings - this fails to work? Did you run > into that scenario? > > --- In [email protected], "bthiesfield" <brot@> wrote: > > > > I've been using it for years in commercial software and it works fine for > > me. It uses the Win32 internet API which has IE3 as it's base requirement, > > so all Windows versions should work. The idea behind using the Wininet > > plugin is that you don't need to configure it - if IE works then it works > > as it uses the OS internet functions. > > > > Brodie > > > > --- In [email protected], "Ask Ari" <arigapudi_s@> wrote: > > > > > > Hi, > > > I used a quick prototype of wininet plugin for 2-way ssl and it worked. > > > Have a few questions - how realible is the gsoap wininet plugin? Is > > > anyone using it in a deployed app without issues? Any gotchas to be aware > > > of? > > > > > > Any special configuration issues? For example: is IE needed? Otherwise, > > > how to install the certificates? Any pointers? > > > Thanks. > > > > > >
