Re: [RFC] Apache::LDAP
James G Smith wrote: Per Einar Ellefsen [EMAIL PROTECTED] wrote: Hi James, At 02:32 02.12.2002, James G Smith wrote: ( Actually, the name is chosen to `rhyme' with Apache::DBI. There are no dependencies on Apache or mod_perl. ) If there is no link with Apache::DBI, I suggest that you choose a more appropriate namespace, like Persistent::LDAP Unfortunately, that's already taken. The module on CPAN implements persistent objects with an LDAP backend (if I read the docs right). Net::LDAP::Persistent is not taken and seems like a good choice to me. --- re: modules discussion lists. Are you sure you are talking about the right list? I thought that module-authors at perl.org is the one for discussing general perl modules. Whereas modules at perl.org is for CPAN namespace registration submission. I've found the latter to be much more helpful, with Tim Bunce usually taking the pains of proposing better namespaces. So whenever I propose a new module I go first to module-authors and if nothing happens I take it to modules, which happens in any case, because I want my modules to be registered. p.s. those module authors who want their modules to be registered (it's not enough to upload the module on CPAN), login into your PAUSE account and go to the registration section. If you have further questions module-authors at perl.org is the place to ask them. __ Stas BekmanJAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide --- http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [RFC] Apache::LDAP
On Sun, 2002-12-01 at 20:32, James G Smith wrote: ( Actually, the name is chosen to `rhyme' with Apache::DBI. There are no dependencies on Apache or mod_perl. ) NAME Apache::LDAP - provides persistent LDAP connections Does this overlap with the ResourcePool series of modules? Chris -- Chris Winters ([EMAIL PROTECTED]) Building enterprise-capable snack solutions since 1988.
Re: [RFC] Apache::LDAP
Chris Winters [EMAIL PROTECTED] wrote: On Sun, 2002-12-01 at 20:32, James G Smith wrote: ( Actually, the name is chosen to `rhyme' with Apache::DBI. There are no dependencies on Apache or mod_perl. ) NAME Apache::LDAP - provides persistent LDAP connections Does this overlap with the ResourcePool series of modules? Thanks. I didn't realize that existed. A search wasn't bringing it up earlier on CPAN, but I probably wasn't using the right terms. It looks like it does a lot of what I want plus a bit more. I think I'll do more browsing of CPAN :/ -- James Smith [EMAIL PROTECTED], 979-862-3725 Texas AM CIS Operating Systems Group, Unix
[RFC] Apache::LDAP
( Actually, the name is chosen to `rhyme' with Apache::DBI. There
are no dependencies on Apache or mod_perl. )
NAME
Apache::LDAP - provides persistent LDAP connections
SYNOPSIS
use Apache::LDAP;
# use Net::LDAP
my $connection = Apache::LDAP - new(
connection = [ # Net::LDAP - new parameters ],
tls = [ # Net::LDAP - start_tls parameters ],
bind = [ # Net::LDAP - bind parameters ],
);
# use Net::LDAPS
my $connection = Apache::LDAPS - new(
connection = [ # Net::LDAPS - new parameters ],
tls = [ # Net::LDAPS - new tls parameters ],
bind = [ # Net::LDAPS - bind parameters ],
);
DESCRIPTION
This module initiates a persistant LDAP connection. The LDAP
access uses the Net::LDAP family of modules.
Since a usable LDAP connection usually requires two or three
steps, Apache::LDAP is not a simple drop-in module in the manner
of Apache::DBI. Code must be written to take advantage of
Apache::LDAP.
Unfortunately, LDAP connections are not sharable across
processes. This means that connections must be made in Apache
children processes, not in the startup process (i.e., during
child initialization, not during server configuration).
Connections are cached based on the class and the parameters
passed to the new method. A previously cached connection is
returned only if the class and parameters are identical to those
used to create the connection and if the connection appears to be
alive. The connection is tested by requesting the root DSA
information from the server.
Net::LDAPS Support
Apache::LDAPS is included with Apache::LDAP to support
Net::LDAPS. The parameters to new are identical. The tls
parameters are included with the connection parameters when
calling Net::LDAPS - new.
SUB-CLASSING
A sub-class of Apache::LDAP may be useful if you want to use an
LDAP module other than Net::LDAP.
package My::Persistant::LDAP;
use base qw(Apache::LDAP);
sub make_connection {
my($class, $params) = @_;
# return new connection
}
sub test_connection {
my($class, $connection) = @_;
# return true if $connection is good
}
__END__
SEE ALSO
the Net::LDAP manpage, the Net::LDAPS manpage.
AUTHOR
James G. Smith [EMAIL PROTECTED]
COPYRIGHT
Copyright (C) 2002 Texas AM University. All Rights Reserved.
This module is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.
--
James Smith [EMAIL PROTECTED], 979-862-3725
Senior Software Applications Developer,
Texas AM CIS Operating Systems Group, Unix
Re: [RFC] Apache::LDAP
Hi James, At 02:32 02.12.2002, James G Smith wrote: ( Actually, the name is chosen to `rhyme' with Apache::DBI. There are no dependencies on Apache or mod_perl. ) If there is no link with Apache::DBI, I suggest that you choose a more appropriate namespace, like Persistent::LDAP -- Per Einar Ellefsen [EMAIL PROTECTED]
Re: [RFC] Apache::LDAP
Per Einar Ellefsen [EMAIL PROTECTED] wrote: Hi James, At 02:32 02.12.2002, James G Smith wrote: ( Actually, the name is chosen to `rhyme' with Apache::DBI. There are no dependencies on Apache or mod_perl. ) If there is no link with Apache::DBI, I suggest that you choose a more appropriate namespace, like Persistent::LDAP Unfortunately, that's already taken. The module on CPAN implements persistent objects with an LDAP backend (if I read the docs right). The problem is that it's generic enough to be made available without requiring a lot of misc. stuff (i.e., part of a larger package), but there's not a good place for it. At least, I'm not thinking of anything. It's also, imho, most useful in an Apache-like environment. I'll keep thinking about it. rant (to noone in particular) I've found this list to be far more helpful than the modules@perl list. I've submitted a fair number of modules to that list with little to no response. While I am thankful for those that have responded, it's never been enough to feel that there was closure. Keep in mind, this is my experience with several modules spread across three-five years (not sure when I first posted to the list). Other people have had different experiences. While I am willing to try it again, my experience makes me shy away from it like a child from a hot frying pan. This rant is in no way meant to start flames. Please do not. I will not respond -- I am just trying to express a small part of my frustration that causes me to post RFCs to the mod_perl list instead of the modules list, even if they are on the edge (or beyond) of mod_perl OT-ness. /rant -- James Smith [EMAIL PROTECTED], 979-862-3725 Texas AM CIS Operating Systems Group, Unix
Re: [RFC] Apache::LDAP
On Sun, 2002-12-01 at 23:40, James G Smith wrote: Per Einar Ellefsen [EMAIL PROTECTED] wrote: Hi James, At 02:32 02.12.2002, James G Smith wrote: ( Actually, the name is chosen to `rhyme' with Apache::DBI. There are no dependencies on Apache or mod_perl. ) If there is no link with Apache::DBI, I suggest that you choose a more appropriate namespace, like Persistent::LDAP Unfortunately, that's already taken. The module on CPAN implements persistent objects with an LDAP backend (if I read the docs right). The problem is that it's generic enough to be made available without requiring a lot of misc. stuff (i.e., part of a larger package), but there's not a good place for it. At least, I'm not thinking of anything. I just did a search on CPAN for `LDAP.' It looks like `Net::LDAP::Persistent' would be a good namespace for your module. At least, I kind of like it. Others may disagree. -- Christopher Grau [EMAIL PROTECTED]
