Hello,
I started looking into wininet under wine and have found a problem
with the dll initialization. My test case is a program running native
using winelib and not a windows executable. I found that WININET_LibMain
was not being called. Because the current dll has all the initialization
logic in WININET_LibMain things where not being initialized. Reviewing
MSDN, it states that dll initialization occurs on InternetOpen. This is
easy enough to do, but i found myself at a loss as to where i should put
the code to free the allocated resources. There appears to be no
definitive closing function call for wininet. One option I was thinking
about is to do reference counting on opens and closes in order to free
the resource after the last close. Is this an acceptable approach?
Is there a standard way for doing this sort of native winelib
initialization being used by other dlls?
thanks
-Aric Stewart
[EMAIL PROTECTED]
