[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: back-perl and password/user synchronization

> -----Original Message-----
> From: Luke Howard [mailto:lukeh@PADL.COM]

> >According to my understanding of perlembed, dSP C macro expects a
> >'PerlInterpreter' pointer called 'my_perl' to have been defined.  But in
> >ldap/servers/slapd/back-perl/perl_back.h  the perl interpreter
> defined is...
> >extern PerlInterpreter *perl_interpreter;
> It worked out of the box with Perl 5.005_03 on a (reasonably) vanilla
> Solaris 8 system.
> Possibly newer versions of Perl have problems?

I think you just lucked out. Perl internals are a nightmare, with different
data structures defined depending on whether you configured for embedded,
threaded, or standalone, and some combinations of the above. My general
experience has been that whatever perl binary was shipped on a system is not
usable in
a threaded/embedded environment, and I always wind up needing to rebuild it.
Life would have been simpler if there had been no separate "standalone"
configuration, and everything used the embedded globals structure by

> On a related note, I think it would be good to extend the interface
> presented by the glue code to allow the backend to return arbitrary
> LDAP result code to the client, not just LDAP_SUCCESS or

Yes, not a bad idea. It would require building some more LDAP-awareness into
your perl code but I suppose that's a reasonable thing to do.
> regards,
> -- Luke
> --
> Luke Howard | lukehoward.com
> PADL Software | www.padl.com

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support