--- Begin Message ---
I understand that the update method can only update the LDAP server object.
It would be great if the update method could also be called to update the
LDIF object. Basically, this is a case where you want to produce an LDIF
containing all the changes that are going to be applied as updates to the
server. If the LDIF file could be read in, compared, and the updates found
for the entry, then the updates returned as a changetype entry object, and
then a new LDIF could be written out with the latest changes that have to be
applied to the entry object.
Cheers, Sion.
Graham Barr wrote:
> On 9 Jun 2004, at 00:44, Sion Camilleri wrote:
> > Extending Net::LDAP::Entry to update against LDIF and LDAP objects
> > could allow the changetype modifications to be to produced.
> >
> > This would be really useful to produce changetypes for entry objects by
> > updating against an LDIF object to produce the changetype LDIF required
> > up to synchronise entry objects.
>
> Can you expand what you mean by that ?
>
> ::LDIF can already read a file with changetype entries and you can
> update a server. It can also create such a file from ::Entry objects
> too.
>
> Graham.
>
> >
> > Graham Barr wrote:
> >
> >> On 8 Jun 2004, at 16:56, [EMAIL PROTECTED] wrote:
> >>> I\'d like to start with a code() method that tries to mimic the
> >>> Net::LDAP one and
> >>
> >> I assume you mean better error handling ?
> >>
> >>> I\'d like to extend the
> >>> Net::LDAP::Entry->update() method so that it takes a
> >>> Net::LDAP::LDIF object as an argument. The latter one
> >>> requires a bit of work in Net::LDAP::LDIF to make it correct.
> >>
> >> Not sure about this one. ::LDIF returns ::Entry objects, so I do not
> >> understand why you want to pass it to a single entry object.. Or did
> >> you mean extend Net::LDAP->update ?
> >>
> >>> P.S: I have implemented a few more controls and will upload
> >>> them to SVN by the end of the week.
> >>
> >> Great
> >>
> >> Graham.
> >
> >
--- End Message ---
