directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ersin Er" <ersin...@gmail.com>
Subject Re: ModifyDN and move semantic
Date Thu, 12 Apr 2007 21:45:54 GMT
As a side note: I prefer single most generic forms for all types of
the same operations. Having more than one forms of search, moddn
causes problems when writing complicated services like authorization
and triggers.

On 4/12/07, Alex Karasulu <akarasulu@apache.org> wrote:
> Yeah I like your idea of using a MoveContext and a RenameContext along with
> a MoveAndRenameContext.  This solves the problem quickly but I wonder if it
> is the best option.
>
> Alex
>
>
>  On 4/12/07, Emmanuel Lecharny <elecharny@gmail.com> wrote:
> > Hi,
> >
> > as I changed the interceptors operation to use instances of ServiceContext
> instead of multiple parameters, I'm facing a difficult semantic problem with
> the modifyDN operation. This operation gather three different semantics :
> > - a rename operation, if the RDN is changed, but not the base DN
> > - a move operation if the RDN is not changed but the base DN is changed
> > - and a move+rename operation if both RDN and base DN are changed
> >
> > As I can't have two move() operations, because the signatureis now the
> same (move(ServiceContext)), so I wanted to rename the method, but which
> name using ? ... Another option would be to keep the two move() methods, but
> instead of using the ServcieContext interface, to use the specific sub-class
> : move( MoveContext ) and move( ChangeContext ), where the MoveContext is
> used if the RDN does not change, and the other one if it change.
> >
> > wdyt ?
> >
> > --
> > Cordialement,
> > Emmanuel L├ęcharny
> > www.iktek.com
>
>


-- 
Ersin
Mime
View raw message