* Brion Vibber [Mon, 17 Aug 2009 09:27:26 -0700]:
> There should be no need for multiple servers in any case; web software
> is pretty good about coexisting. ;)
>
Wouldn't a truly robust comparsion require two separate AMP's instead of
simple apache virtual hosts?
> Multiple versions of MediaWik
--- On Mon, 8/17/09, Brion Vibber wrote:
> Really though, this thread has gotten extremely unfocused;
> it's not
> clear what's being proposed to begin with and we've
> wandered off to a
> lot of confusion.
I'll take partial responsibility for the confusion. Like I said recently, I
think it
There should be no need for multiple servers in any case; web software
is pretty good about coexisting. ;)
Multiple versions of MediaWiki can sit side by side in separate
directories with no trouble. You can even run multiple versions of PHP
simply by setting them up as FastCGI applied to di
* Platonides [Mon, 17 Aug 2009 00:06:59 +0200]:
> In fact, I'm not sure to have understood the problem. I find the
> proposed options quite bizarre. So if you have understood the
> "specification", please enlighten me. :)
>
If I had to check whether there are any regressions between versions at
t
I feel uncomfortable ignoring this kind of response on this or any
list, so I will say this at the risk of being personally attacked.
I'm certain that treating people this way detracts from both
motivation and productivity - for volunteers and staff alike.
Responses like this lack any sense o
Dmitriy Sintsov wrote:
> I've compiled so-called thread-safe version of PHP and the corresponding
> MPM long time ago, before I've used MediaWiki (I use it since v1.9.3).
> I've had various problems and instability with such setup. It seems that
> not much changed since then:
> http://neosmart.n
* Platonides [Sat, 15 Aug 2009 23:32:44 +0200]:
> You can compile PHP both thread safe or non-thread safe (note that if
> some php extension isn't really thread safe, it will break the
server).
>
> If you aren't using a sapi based on threads, it doesn't make sense to
> compile php thread safe, si
dan nessett wrote:
> On the other hand, maybe you would rather code than think
> strategically. Fine. Commit yourself to fixing the parser so all of
> the disabled tests run and also all or most of the pages on
> Wikipedia do not break and I will shut up about the CPRT. Commit
> yourself to creatin
On Fri, Aug 14, 2009 at 8:37 PM, dan nessett wrote:
> While my machine was compiling AMP components, I thought about this a little
> bit. It seems weird that the implementation of a language intended to provide
> backend functionality for web servers isn't thread safe. Apache and other web
> ser
dan nessett wrote:
> --- On Fri, 8/14/09, Dmitriy Sintsov wrote:
>
>> I remember some time ago I was strongly discouraged to
>> compile and run
>> PHP threaded MPM for apache because some functions or
>> libraries of PHP
>> itself were not thread safe.
>
> While my machine was compiling AMP co
--- On Fri, 8/14/09, Tim Starling wrote:
> And please, spare us from your rant about how terrible this
> is. It's
> not PHP's fault that you don't know anything about it.
I'm sorry my questions make you angry. I don't recall ranting about PHP.
Actually, I kind of like it. Lack of thread safety
* Tim Starling [Sat, 15 Aug 2009 11:36:43
+1000]:
> I think if you spent half as much time reading the PHP manual as
> posting clueless questions to this list, you would know that neither
> of the first two options can work. Namespaces because even if we did
> use them, the different versions wou
dan nessett wrote:
> One of the first problems to solve in developing the proposed CPRT
> is how to call a function with the same name in two different MW
> distributions. I can think of 3 ways: 1) use the Namespace facility
> of PHP 5.3, 2) use threads, or 3) use separate process and IPC.
> Since
--- On Fri, 8/14/09, Dmitriy Sintsov wrote:
> I remember some time ago I was strongly discouraged to
> compile and run
> PHP threaded MPM for apache because some functions or
> libraries of PHP
> itself were not thread safe.
While my machine was compiling AMP components, I thought about this a
--- On Fri, 8/14/09, Dmitriy Sintsov wrote:
> I remember some time ago I was strongly discouraged to
> compile and run
> PHP threaded MPM for apache because some functions or
> libraries of PHP
> itself were not thread safe.
OK, this and Chad's comment suggests the option is multi-process/IPC.
* dan nessett [Fri, 14 Aug 2009 08:31:03 -0700
(PDT)]:
> One of the first problems to solve in developing the proposed CPRT is
> how to call a function with the same name in two different MW
> distributions. I can think of 3 ways: 1) use the Namespace facility of
> PHP 5.3, 2) use threads, or 3)
On Fri, Aug 14, 2009 at 11:31 AM, dan nessett wrote:
> One of the first problems to solve in developing the proposed CPRT is how to
> call a function with the same name in two different MW distributions. I can
> think of 3 ways: 1) use the Namespace facility of PHP 5.3, 2) use threads, or
> 3) u
One of the first problems to solve in developing the proposed CPRT is how to
call a function with the same name in two different MW distributions. I can
think of 3 ways: 1) use the Namespace facility of PHP 5.3, 2) use threads, or
3) use separate process and IPC. Since MAMP supports none of thes
18 matches
Mail list logo
