Re: libxml2/threading/win 2003

Andi Gutmans wrote:

Yeah but Windows is very friendly and designed for this. As long as the dlls are in the application's directory you will not have problems. This is actually much easier and straightforward than on Linux so it sounds to me that dll clashing problems (which doesn't happen in this case) means that either the .zip or the .msi were just putting the dll not in the right place. That's an easy fix. Seriously, if there's one thing that Windows is good at is in a friendly dll search order. They designed it so that you can keep dlls with the app. Not that I am trying to squash the use of dlls here, but I'm not sure you are following me.

Why would the dll in the directory with the php5ts.dll take precedence over another version of the lib somewhere else? For instance, under apache, some other module is loaded first that also happens to use libxml2.dll (and happens to include it within its directory). If this module gets loaded before PHP, what would the search order for the dll be then. I assume its own directory and then the windows directories. PHP would then end up using the other dll (already being loaded into the apache space) and not the one in its own directory. Same would then hold true for the iconv, etc.. CLI on the other hand would (at least should) always use the one within the PHP directory. Rob