Caroline Maynard wrote:
On 01/12/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Do you think that we should build with the thread safe libs by default?
or have 2 bin libraries one thread safe, one not but faster?
The question applies to both Linux and Windows, and I'm not sure but we
may have different answers for different systems.
This isn't important for the PHP implementation, because we build the
Tuscany code from source at present, so all we need is a compile
switch. But
in general, the expectation is that binaries are provided for Windows,
but
*IX users will build it themselves.
Caroline, maybe I missed it in the email thread, but do your users need
this on Linux? Windows? both?
Both. Actually anywhere where they might be running an Apache HTTP Server
with a threaded MPM and MOD_PHP. For example FreeBSD, Linux AMD_64 or
Mac OS
X, to name but a few.
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...
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?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
