Re: wininet: prevent memory leak and superfluous status notifications

[Steven Edwards]

Hello Kevin,

--- Kevin Koltzau <kevin(a)plop.org> wrote:
> Under Windows, InternetOpenUrl only sends one
> INTERNET_STATUS_HANDLE_CREATED and the
> handle created by this function only creates one
> INTERNET_STATUS_HANDLE_CREATED when closed

While you are working on the wininet stuff... If you have time could
you look at a way to be able to make use of Winsock on the mingw port?
We wanted to  convert wininet to winsock but Alexandre says this will
be to slow on Unix so we need to do something the wininet souce to be
able to make it use Unix sockets on Unix and Winsock on the windows
port. I dont really understand or know how this should be done as I
never really have done any socket programing. If you could fix it for
Wininet or point me to a example then I can try and do it for other
dlls we might want to share on the Windows port. I am thinking about
trying to port our ICMP.dll to Winsock also for the Mingw/ReactOS port
but once again it needs to be able to do both Winsock and Unix Sockets.

Thanks
Steven



	
		
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861

wininet: prevent memory leak and superfluous status notifications

[Kevin Koltzau]

On Thursday 13 May 2004 01:04 pm, Steven Edwards wrote:
> While you are working on the wininet stuff... If you have time could
> you look at a way to be able to make use of Winsock on the mingw port?
> We wanted to  convert wininet to winsock but Alexandre says this will
> be to slow on Unix so we need to do something the wininet souce to be
> able to make it use Unix sockets on Unix and Winsock on the windows
> port. I dont really understand or know how this should be done as I
> never really have done any socket programing. If you could fix it for
> Wininet or point me to a example then I can try and do it for other
> dlls we might want to share on the Windows port. I am thinking about
> trying to port our ICMP.dll to Winsock also for the Mingw/ReactOS port
> but once again it needs to be able to do both Winsock and Unix Sockets.

I could take a look at it once I finish with a few other changes I have planned
for wininet, not sure when that will be exactly however (at least a week or two).