Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.1.5

Request #9681 LDIF reading and writing
Submitted: 2006-12-22 12:06 UTC
From: b dot hallinger at skyforcesystems dot de Assigned: beni
Status: Closed Package: Net_LDAP (version CVS)
PHP Version: Irrelevant OS:
Roadmaps: 1.1.0    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 42 - 25 = ?

 
 [2006-12-22 12:06 UTC] b dot hallinger at skyforcesystems dot de (Benedikt Hallinger)
Description: ------------ I think a class for LDIF reading/writing similar to perls would be nice: http://search.cpan.org/~gbarr/perl-ldap/lib/Net/LDAP/LDIF.pod However this has no high priority at the moment.

Comments

 [2007-10-16 14:22 UTC] beni (Benedikt Hallinger)
A LDAP class copy could be implemented, that serves as dummy server on ldif files. A factory method in Net_LDAP needs to return an Net_LDAPLDIF object which parses the calls to Net_LDAP to act on an LDIF File.
 [2007-12-28 07:28 UTC] beni (Benedikt Hallinger)
LDIF reading support should be working now (as of yesterday evening), writing support will follow soon.
 [2008-01-07 08:08 UTC] beni (Benedikt Hallinger)
Writing should work too, but some options are still not implemented.
 [2008-01-08 15:10 UTC] beni (Benedikt Hallinger)
Write options are implemented; however the modrdn entry operation as well as the "raw" (and auto-schema) option is not implemented yet.
 [2008-01-17 12:40 UTC] beni (Benedikt Hallinger)
Most things are implemented now, however "modrdn" and "add" changesets are still missing. There is a problem to detect if an entry is going to be moved. Most probably a new method must be implemented for this.
 [2008-01-21 08:20 UTC] beni (Benedikt Hallinger)
Nearly all features are implemented. Missing features will be implemented as per request (or by time) since they are most probably very rarely used.