> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
>
> > Is the difference that in both cases the component doing
> > the lookup is intended to perform operations on *all* returned
> > services, as opposed to just selecting one of them?
>
>
> That is a key question. With arrays, I have a sneaking
> suspiscion that the exact indexes of the components will
> change as we change the number of components. That can spell
> disastor for someone who is banking on the behavior of
> component 6 returned from an array. If the array is smaller
> we get an IndexOutOfBoundsException. If the array has a new
> element inserted at position 5, then what used to be 6 is now 7.
That's exactly the type of behavior that should not be allowed.
What I want is for the array return to have no guarantees as
to its length or the specific indexes - and as far as I can tell,
this is the case.
But the Map return - what does it guarantee in terms of key -> value
mapping? What type is the key? I don't like it.
> > But with Map / Array lookup you'd:
> >
> > 1. lookup Map / Array
> > 2. foreach Service service in Map/Array do service.method ()
>
>
> I don't like this from a security perspective. What you are
> doing is making it alot easier to write trojan components
> that operate on all the services. In essence we are giving
> up too much control.
I disagree. You still have to specify each component in the array in the
assembly config.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
