in reply to Re^2: Recommendations for an IIS intranet
in thread Recommendations for an IIS intranet

Net::LDAP not being maintained is not an issue. In fact, it points to the fact that LDAP as a technology is currently relatively static because it does it's job, works quite well, and is extensible without having to muck with the internals of LDAP.

Just because something isn't obviously maintained isn't enough to signify a dead/rotting library. You need to look into its maturity level, and whether it is being used a lot. LDAP is a wonderfully useful tool, that is used a lot, but it's quiet enough that many smaller shops may not have been introduced to it yet. The fact that Active Directory is built on top of LDAP is something Microsoft would rather not advertise. But that fact alone is enough to tell you that it won't be going away any time soon.

-Scott

  • Comment on Re^3: Recommendations for an IIS intranet

Replies are listed 'Best First'.
Re^4: Recommendations for an IIS intranet
by Bloodnok (Vicar) on Apr 17, 2009 at 21:57 UTC
    If you'll forgive me, you appear to be mistaking the maturity of DAP/LDAP technology with that of Net::LDAP - the perl interface library to it.

    The maturity of the DAP/LDAP technology and its volume of usage was and is, not in question - I only questioned the maintenance levels of the library since when last I had occasion to use it in anger, there were a couple of shortfalls - related, as it happens, to the M$/LDAP crossover (M$, in not atypical fashion i.e. in a manner similar to Java etc., took LDAP and modified it to their own ends & needs such that AD only partially resembles LDAP).

    A user level that continues to overstate my experience :-))
[reply]

In Section Seekers of Perl Wisdom