From dev-return-21847-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Wed Oct 03 14:50:16 2007 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 81496 invoked from network); 3 Oct 2007 14:50:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2007 14:50:14 -0000 Received: (qmail 42261 invoked by uid 500); 3 Oct 2007 14:50:02 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 42232 invoked by uid 500); 3 Oct 2007 14:50:01 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 42221 invoked by uid 99); 3 Oct 2007 14:50:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 07:50:01 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.146.183 as permitted sender) Received: from [209.85.146.183] (HELO wa-out-1112.google.com) (209.85.146.183) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 14:50:03 +0000 Received: by wa-out-1112.google.com with SMTP id m38so6172499waf for ; Wed, 03 Oct 2007 07:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=1Swihj906I1GxN1rzNJWPs1bz9Trpw1RYihGo6VR3NU=; b=UkWMh4Dp0GCIu8Di6y0SvOtZGl63ieXICFelnNq4fo11EBA03Qu5xhGegVwzALinUYe/uLXMhotxLoJIu9lvYFptkMrrDzDm8Af6vu4FIb5Ljb82XrRDHY8GvUsYc0WH94P2t9QcnHYOg9u1aHMtSFFvQF91wixFlzNdl7ALsMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=n2aFL23x7y2LmJ6wpS1g8Zq8Kmg9A1zLdPP+MPfIItiYc12V0aaisiTr9qWOsGyEg2jYp0AAyRfWdo9cixukOtV4MDZiXDjdQkSHvnF/w2G21mm4AigQ9FRvabRDsf+ir1Y/XPm6Z8ZsIf2OrVSZ92XxKirn3DwAL/hNsn0t5gg= Received: by 10.114.152.17 with SMTP id z17mr4203153wad.1191422981965; Wed, 03 Oct 2007 07:49:41 -0700 (PDT) Received: by 10.115.76.8 with HTTP; Wed, 3 Oct 2007 07:49:41 -0700 (PDT) Message-ID: Date: Wed, 3 Oct 2007 10:49:41 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" , elecharny@iktek.com Subject: Re: [jira] Created: (DIRSERVER-1081) Injecting more information in the opContext structure In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_22853_29882181.1191422981962" References: <32272304.1191415550639.JavaMail.jira@brutus> X-Google-Sender-Auth: 4f5db0a2e1393d4b X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_22853_29882181.1191422981962 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I don't know if this is a good idea since the registries are services - I'd leave it up to dependency injection to handle populating dependent services like the interceptors. You're also presuming that these registries will be used only in the code (methods) dealing with request processing. There are other places where they are used. Also you cannot split up the registries just for a specific partition. Maybe I did not understand properly because does not make sense. Can you clarify? Alex On 10/3/07, Emmanuel Lecharny wrote: > > yes > > On 10/3/07, Alex Karasulu wrote: > > What registries are you referring to? Schema registries? > > > > Alex > > > > > > On 10/3/07, Emmanuel Lecharny (JIRA) wrote: > > > Injecting more information in the opContext structure > > > ----------------------------------------------------- > > > > > > Key: DIRSERVER-1081 > > > URL: > > https://issues.apache.org/jira/browse/DIRSERVER-1081 > > > Project: Directory ApacheDS > > > Issue Type: Improvement > > > Affects Versions: 1.5.1 > > > Reporter: Emmanuel Lecharny > > > Fix For: 2.0.0 > > > > > > > > > As each server operations now use this opContext for every operations= , > it > > would be useful to inject more information into this context, like > access to > > the registries, or other things which are currently stored locally in > each > > interceptors during the initialization phaze. > > > > > > It will be more elegant, will allow global modification of the server > > without having to reinit all the interceptors, and could help to define > > specific operation's context for a request (for instance, if we think > about > > an operation associated to a specific partition, we could perfectly > inject > > the partition associated registries, allowing us to have per-partition > > regristries, instead of one single registries set for all the partition > - > > just an idea) > > > > > > -- > > > This message is automatically generated by JIRA. > > > - > > > You can reply to this email to add a comment to the issue online. > > > > > > > > > > > > > -- > Regards, > Cordialement, > Emmanuel L=E9charny > www.iktek.com > ------=_Part_22853_29882181.1191422981962 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I don't know if this is a good idea since the registries are services -= I'd leave it up to dependency injection
to handle populating depen= dent services like the interceptors.  You're also presuming that t= hese registries
will be used only in the code (methods) dealing with request processing= .  There are other places where they
are used.

Also you cann= ot split up the registries just for a specific partition.  Maybe I did= not understand properly because=20
does not make sense.  Can you clarify?

Alex

On 10/3/07, Emmanuel= Lecharny <elecharny@gmail.co= m> wrote:
yes
On 10/3/07, Alex Karasulu <akar= asulu@apache.org > wrote:
> What registries are you referring to? Schema regist= ries?
>
> Alex
>
>
> On 10/3/07, Emmanuel Lec= harny (JIRA) <jira@apache.org >= ; wrote:
> > Injecting more information in the opContext structure
>= > -----------------------------------------------------
> >> >           = ;       Key: DIRSERVER-1081
> >=             &nb= sp;     URL:
> h= ttps://issues.apache.org/jira/browse/DIRSERVER-1081
> > &= nbsp;           &nbs= p;Project: Directory ApacheDS
> >     &nb= sp;     Issue Type: Improvement
> >     Affects Versions: 1.5.1
> >&= nbsp;            Rep= orter: Emmanuel Lecharny
> >      &n= bsp;       Fix For: 2.0.0
> >> >
> > As each server operations now use this opContext f= or every operations, it
> would be useful to inject more information into this context, like= access to
> the registries, or other things which are currently stor= ed locally in each
> interceptors during the initialization phaze.
> >
> > It will be more elegant, will allow global modif= ication of the server
> without having to reinit all the interceptors= , and could help to define
> specific operation's context for a r= equest (for instance, if we think about
> an operation associated to a specific partition, we could perfectl= y inject
> the partition associated registries, allowing us to have p= er-partition
> regristries, instead of one single registries set for = all the partition -
> just an idea)
> >
> > --
> > This messa= ge is automatically generated by JIRA.
> > -
> > You can = reply to this email to add a comment to the issue online.
> >
> >
>
>


--
Regards,
Cordialement,
Emm= anuel L=E9charny
www.iktek.com
<= /blockquote>

------=_Part_22853_29882181.1191422981962--