Front page | perl.perl5.porters |
Postings from July 2001
Re: Case for XML-RPC
From:
Bart Schuller
Date:
July 18, 2001 01:03
Subject:
Re: Case for XML-RPC
Message ID:
20010718100036.C20370@tanglefoot.lunatech.com
On Wed, Jul 18, 2001 at 01:59:43AM -0400, Adam Turoff wrote:
> On Tue, Jul 17, 2001 at 11:57:05PM -0400, Simon Cozens wrote:
> > If it helps sway the issue, Python-dev is considering putting the whole
> > of expat (yes, a whole THREE FILES) into their core.
>
> I vaguely remember hearing something about expat with XML::Parser
> conflicting with expat in Apache when running mod_perl.
>
> Can anyone confirm this? How huge of an issue is it?
It's just the generic issue that apache statically links expat and then
things blow up when perl (linked to apache) starts dynamically loading
the same symbols. The solution is real easy: have apache link to the
same dynamic version as perl.
What doesn't help in this case is that the original expat library did
not ship with support for making it a shared library. That support was
written as part of the maintenance of XML::Parser (which also included a
private copy) and is now continueing in the sourceforge version, which
can now be called *the* version of expat.
The history of expat teaches us that it is bad to bundle it, and good to
package it as a real library using current community standards
(./configure --prefix=/bla;make;make install), which can then be used by
everything that needs it. For example, the PHP module had exactly the
same problem.
Instead of bundling C libraries with perl, it would make more sense to
provide a platform independent Debian-like distribution of libraries.
Because expat may not even be the best choice. If you follow the
perl-xml world you'll have noticed that the gnome libxml2 and libxslt
libraries offer extremely good performance, and rapidly developing perl
support. Does that mean that perl should ship with glib, libxml2 and
libxslt? I'd hope not.
--
The idea is that the first face shown to people is one they can readily
accept - a more traditional logo. The lunacy element is only revealed
subsequently, via the LunaDude. [excerpted from the Lunatech Identity Manual]