[horde] language

[Eric Rostetter]

Quoting Daniel Eckl <daniel.eckl at gmx.de>:

> The benefit is clear: Get rid of a not thread-safe prerequisite to get horde
> run perfectly with modern webserver technology.

The non thread safe prerequisite is php, not gettext.  I don't think we
can get rid of php.  So it would be better to work with the php folks to
get php to be thread safe, not to change every php application to work
around php limitations.

> I believe you wanted to say: "Yes, that would fix the problem with the
> languages
> on multi-threaded apache, but this is a incredible amount of work, we would
> loose the good gettext format and it's not worth it in my opinion."

Or, perhaps in addition, rather than each project using php (say X projects)
circumventing the problem, we can have just one project (php itself) fix
the problem.

Instead of X projects spending Y time to circumvent the problem, causing
X*Y man hours spent, we can just spend Y time fixing php, causing just Y
man hours spent, and all future projects benefit without any time being
spent on it.

> I prefer the whole truth instead of a part that sounds easy to understand.

Okay.  The whole truth is horde isn't broken.  The limitation is in php.
So the proper place to fix it is in php, not horde.

> Okay, then thanks all of you for the help and the wonderful ideas :)
>
> Greets,
> Daniel

--
Eric Rostetter
The Department of Physics
The University of Texas at Austin

Why get even? Get odd!