Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [higgins-dev] new IdASRegistry

Of course this is just the "long way" of doing things (get list of factories for ContextId -> select a factory -> use factory to instantiate context).

By now there's also a convenience method in the registry that simple takes a ContextId (typed either as String or IContextId) and returns an instantiated IContext. However, this will only work once we / I changed the IContextFactory interface to use ContextIds instead of ContextRefs.

Markus

On 8/7/07, Markus Sabadello <msabadello@xxxxxxxxxxxxx> wrote:

As shown in the examples on the wiki page http://wiki.eclipse.org/ContextDiscoveryComponent , the registry has a method getContextFactories(), which can be passed a context type (String) or a ContextId, and returns a list of potential factories. As long as the underlying XRDs do not change, this list always contains the same factories in the same order.

Markus


On 8/7/07, Paul Trevithick < paul@xxxxxxxxxxxxxxxxx> wrote:

I'd rather not have the IdAS registry remember the binding.  As long as IdAS consumer can, for a given ContextId, (a) get the list of potential factories and (b) choose which one it wishes to use, that should be good enough.

 

From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Markus Sabadello
Sent: Monday, August 06, 2007 11:29 AM
To: Higgins (Trust Framework) Project developer discussions
Subject: Re: [higgins-dev] new IdASRegistry

 


Hmm I don't know enough about the use cases to have an opinion about this. Has anyone ever used different context factories for the same context?

The current proposal does support associating a context with a single or multiple context factories (via the context type), but as you say it does not really "remember" which one was used. However, due to the "priority" attributes in XRDS, one can predict which one the registry will choose.

Markus

On 8/6/07, Greg Byrd <gbyrd@xxxxxxxx> wrote:

When we first discussed the registry, a few F2F's ago, there was a
notion that the registry would hold a binding of a context and a
particular context factory.  Different factories might allow different
operations/views of a given context, so it's important for a user to
keep using the same factory in order to get a consistent experience.

I don't see anything in the current proposal that supports this.  Do we
still believe that it's needed?  Do we believe that different factories
will indeed have different behaviors?  (Even if this behavior is subtle,
such as different ways of updating attributes, it might be confusing if
the user sees differences.)

...Greg



Markus Sabadello wrote:
> Hi all,
>
> Since I didn't get much feedback about the new XRI/XRDS based
> IdASRegistry, I am wondering if you guys (especially Jim and people
> working on Context Providers) had a chance to look at it.
>
> I would like to check it in soon so we can get this running, and it
> will definitely break a few things. The changes will include replacing
> ContextRefs with ContextIds in the IContextFactory interface.
>
> The relevant Wiki pages are:
> http://wiki.eclipse.org/ContextId
> http://wiki.eclipse.org/Context_Discovery
> http://wiki.eclipse.org/ContextDiscoveryComponents
>
> If noone objects I propose to commit this in a few days.. Let me know
> if I can help with anything.
>
> Markus
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev
>

_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev

 


_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev





Back to the top