[csw-users] PHP - Solaris LDAP libraries vs. OpenLDAP libraries

[Luke Youngblood]

Mark,

I think that would be an excellent solution although it sounds like a lot of
extra work on your part.  It does seem that as PHP grows to accommodate more
and more back-end database support and authentication mechanisms this will
be a good long term solution.  It should also keep the memory footprint down
as you can build PHP with only the components you need.

I also think that it would be a good idea to submit a bug to either PHP or
OpenLDAP, but it's still a little unclear to me which component is causing
the segfault, and I've never submitted a bug like this to Zend or OpenLDAP
before.  If you'll point me in the right direction I'd be happy to share any
information I have with them.

In regards to your last question, I'm willing to help troubleshoot and
determine if this happens with other packages.  Can you give me an example
of another package linked against OpenLDAP that does a get(whatever)byname?
Preferably a CSW package of course... :-)

Thanks a ton for all of the hard work that you guys do.  Now that I have a
Solaris 10 box at home perhaps I can begin to contribute a little in my
spare time to "give back" to you guys that give us so much, without asking
anything in return.

Regards,
Luke

-----Original Message-----
From: users-bounces at lists.blastwave.org
[mailto:users-bounces at lists.blastwave.org] On Behalf Of Mark Round
Sent: Friday, February 18, 2005 5:07 AM
To: questions and discussions
Subject: Re: [csw-users] PHP - Solaris LDAP libraries vs. OpenLDAP libraries

Now that I've had some time to mull over this problem, I believe I may
have a solution to it. It would also accomodate both people who want
to use the OpenLDAP libraries, and those that experience
incompatibilities and segfaults if they don't use the Sun-provided
libraries.

I'll try and make PHP modular. Most of the extensions to PHP can be
built as loadable modules, which can be loaded or unloaded on demand
via the php.ini file. Going down this route would provide a small
"core" PHP package. You could then add on the extensions you need to
it - for example, database support would be provided by php4_pgsql,
php4_mysql, php4_odbc and the like. I could then try and build two
different PHP LDAP modules - so depending on your situation, you could
pkg-get either php4_openldap or php4_sunldap.

This would also mean that instead of a monolithic libphp4.so, users
could tailor their PHP installation to suit their needs, only loading
in the additional modules they would actually use.Obviously, this will
require some extra work on the packaging front, but I think it would
be well worth it. Comments, feedback, etc. all appreciated!

After the release of PostgreSQL 8 and related packages (which will be
"real soon now"), I'll make this a top priority. Luke - I'd also be
interested in taking up the original segfaulting issue with either the
PHP or OpenLDAP developers - does the segfaulting issue happen in any
program that does a get(whatever)byname when linked to OpenLDAP, or
does it seem to be a PHP-specific issue ?

Ta,

-Mark
_______________________________________________
users mailing list
users at lists.blastwave.org
https://lists.blastwave.org/mailman/listinfo/users