RE: Exceptions (was: RE: [Avalon4:PROPOSAL] Context Consensus)

> I (as spokesperson for Merlin) can gaurantee you that the object
> provided to you will be castable to you requested interface and
> that it will be supplid with the requested keys fully populated
> and that each key value will be castable to the requested interface.

Well, I'm not a big fan of such dependency upon external configuration
files, but that's a moot point.  You can do that in the context (small c) of
current Avalon containers and conditions.

However, we've already seen one developer wanting to expand Avalon to use
JINI, for example.  Any component can ask for any other component at any
time in a dynamically populated environment.  How do you expect to make JINI
compliant, or any other dynamically populated environment?  I understand
that you don't expect to be there before AV5.

	--- Noel