The move to apache2 has been compared,
and I think that's another example where the move should be done.
It has support for
threading, so when a new request comes in, an entire server process
doesn't have to be
forked! What a tremendous potential resource savings if all hosts
were to just
switch...
I sent this to a co-worker in March of last year -
. . . Windows likes to use threads within processes rather than
additional processes.
That is a design decision. UNIX systems can create and destroy
processes very quickly, while creating and destroying threads on
UNIX systems takes longer. Windows is the opposite, threads are
fast to create/destroy. That is the main reason apache2 has
different MPMs. One optimized for UNIX-style systems, and one for
Windows. The problem with that is now programmers can go hog wild
and create MPMs for no apparent reason besides the fact that they
can ;) It gets confusing.
That's why the big warning about PHP and apache2. Because you can
run a threaded MPM, there are some libraries that PHP links to that
don't understand threads, even if PHP does. If you use a process-
based MPM with apache2, then you won't get data synchronization
issues while using PHP.
The threaded MPM is only an advantage on Windows, it isn't a
_universal_ advantage.
I read through the SM thread. At some point, PHP4 will not be
updated, so a transition to PHP5 _will_ be required. The question is,
does RoundCube choose how and when the transition happens, or allow
external forces ( PHP developers ) to dictate the timeline ?
I understand that RoundCube currently can run on PHP5, although I
have not done so myself. To encourage PHP5 use, why not list it in
the requirements as "will run using PHP5" or "tested using PHP5"
The 5/2/2008 date seems to be as good as any to pick. If a PHP4-
compatible release is made some time before the transition date, then
users forced to use PHP4 can use that older release. If there remains
a large PHP4 user base, security changes could be back-ported to that
PHP4-compatible RoundCube release. If the PHP4 user base isn't
interested in doing the work to back port those security updates,
then there isn't much use for it.
Code changes that are security only would have to be announced, so
that those that do the back porting know there is work to be done.
Maybe version 1.0 of RoundCube is the last PHP4-compatible release ?
Charles Dostale
System Admin - Silver Oaks Communications
http://www.silveroaks.com/
824 17th Street, Moline IL 61265
