You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2007/10/03 14:45:50 UTC
[jira] Created: (DIRSERVER-1081) Injecting more information in the
opContext structure
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.
Re: [jira] Created: (DIRSERVER-1081) Injecting more information in the opContext structure
Posted by Alex Karasulu <ak...@apache.org>.
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 <el...@gmail.com> wrote:
>
> yes
>
> On 10/3/07, Alex Karasulu <ak...@apache.org> wrote:
> > What registries are you referring to? Schema registries?
> >
> > Alex
> >
> >
> > On 10/3/07, Emmanuel Lecharny (JIRA) <jira@apache.org > 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écharny
> www.iktek.com
>
Re: [jira] Created: (DIRSERVER-1081) Injecting more information in the opContext structure
Posted by Emmanuel Lecharny <el...@gmail.com>.
yes
On 10/3/07, Alex Karasulu <ak...@apache.org> wrote:
> What registries are you referring to? Schema registries?
>
> Alex
>
>
> On 10/3/07, Emmanuel Lecharny (JIRA) <jira@apache.org > 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écharny
www.iktek.com
Re: [jira] Created: (DIRSERVER-1081) Injecting more information in the opContext structure
Posted by Alex Karasulu <ak...@apache.org>.
What registries are you referring to? Schema registries?
Alex
On 10/3/07, Emmanuel Lecharny (JIRA) <ji...@apache.org> 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.
>
>
Re: [jira] Created: (DIRSERVER-1081) Injecting more information in the opContext structure
Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi David,
I'm not thinking about interceptor specific data, but generic
informations. To me, we have a lot of structure which are associated
during the interceptor initialization which are not associated with
the interceptor itself, but as the operation needs them, we have added
them in the init phase. Not sure this was the best idea, because that
means you have to create a lot of static variables all over the
interceptors.
I'm not sure that the cost of passing a new element in the opContext
will be measurable...
Anyways, we have to discuss further what I have in mind, because it's
a little bit fuzzy for me too atm ;)
On 10/3/07, David Jencks <da...@yahoo.com> wrote:
> I tend to think this is not a very good idea or else I don't
> understand it. I think the interceptors will be clearest if they are
> injected (by spring or external setup code) with whatever information
> they need to do their job that is not request specific and the
> opContext objects are setup with only the request-specific
> information. Likewise the opContext object will be quickest to setup
> the less information they have in them.
>
> thanks
> david jencks
>
> On Oct 3, 2007, at 5:45 AM, 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écharny
www.iktek.com
Re: [jira] Created: (DIRSERVER-1081) Injecting more information in the opContext structure
Posted by David Jencks <da...@yahoo.com>.
I tend to think this is not a very good idea or else I don't
understand it. I think the interceptors will be clearest if they are
injected (by spring or external setup code) with whatever information
they need to do their job that is not request specific and the
opContext objects are setup with only the request-specific
information. Likewise the opContext object will be quickest to setup
the less information they have in them.
thanks
david jencks
On Oct 3, 2007, at 5:45 AM, 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.
>
[jira] Updated: (DIRSERVER-1081) Injecting more information in the
opContext structure
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1081:
-----------------------------------------
Fix Version/s: 2.0.0-RC1
(was: 2.0.0)
Moved back to 2.0.0-RC1
> 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-RC1
>
>
> 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.