- From: Jose Kahan <jose.kahan@w3.org>
- Date: Tue, 14 Aug 2001 18:16:01 +0200
- To: Oliver Steinau <Oliver.Steinau@STencode.de>
- Cc: www-lib@w3.org
Hello Olivier, Thanks for your report. As far as I could tell, your analysis is correct. I erased the #ifdef in this function. It now looks like the other ones. I commited the change to CVS too. If this patch causes a problem to someone, please report it to the list. I will look at your other reports later this week (tomorrow is a holiday in France). -jose On Tue, Aug 14, 2001 at 10:54:21AM +0200, Oliver Steinau wrote: > I need some help with the HTProfile_newPreemptiveClient... > > HTProfile_newPreemptiveClient looks like: > > PUBLIC void HTProfile_newPreemptiveClient (const char * AppName, > const char * AppVersion) > { > /* Do the default setup */ > client_profile(AppName, AppVersion, YES, NO, NO); > > /* On windows we need the initialization anyway */ > #ifdef WWW_WIN_ASYNC > HTEventInit(); > #else > /* Remember that we are loading preemptively */ > preemptive = YES; > #endif > } > > > I have two questions concerning this piece of code: > 1. HTEventInit is *ONLY* called if WWW_WIN_ASYNC (and not, eg. if > WWW_WIN_DLL), > despite the comment. Bug? > 2. "preemptive = YES;" is only done if the WSAAsyncXXX calls are not > used; but > what has preemptive/non-preemptive to do with async calls? > > The effect is, that when you build with WWW_WIN_DLL (no WWW_WIN_ASYNC) > and create > a preemptive client, *NOTHING* works, because WSAStartup is never > called... > > As far as I can see, HTEventInit takes care of async or not; so it seems > that > all preprocessor commands should be deleted from this function -- am I > right?
Received on Tuesday, 14 August 2001 12:17:35 UTC