On 01/12/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
OK, I was asking because it seems more interesting to support threaded MPMs on Windows (as a threaded MPM is the default) than on Linux/Unix where I think the majority of people use forking/multi-process MPMs. So I was initially thinking of having the default binary distribution be multi-threaded on Windows and mono-threaded on Linux, but I'm interested in your input and what you've seen in terms of "actual" usage on both platforms. We know that, as you said, pretty much all options are possible on all platforms, and people are expecting binary distributions on Windows but in general build from source on Linux, but I'm looking for the right defaults...
I would agree with those defaults for the binaries, provided there's no negative effects for the non-threaded Windows user.
Have you considered how to maintain the status of the thread-safe > variant as new code is added? What do you mean by "maintain the status of the thread-safe variant"? document it? continue to make sure that it works when adding new code? anything else?
I meant the latter - with quite a few different people contributing code and patches, there's a likelihood that new thread-unsafe code may be introduced. -- Caroline
