RE: [Avalon4:PROPOSAL] Context Consensus

> From: Nicola Ken Barozzi [mailto:[email protected]]
> > Berin:
> > 
> >>As impacting Framework 5+, I would like to see a flexible context
> >>that has very strong contracts--i.e. if you want a BlockContext,
> >>you get one with no casting, if you want a ServletContext 
> same thing.
> > 
> > If there is such a solution, I'm for it, too.  Do you have 
> a suggestion that
> > is BOTH strongly typed AND extensible?
> 
> Personally, I don't like castings, and anything that can make it less 
> "scary" I like. Hence I think your idea is interesting.
> I like using the service classname to ask for a service to the 
> servicemanager, but some like opaque keys. Hence the above 
> example can 
> be applied there too.

I was thinking of "Zen" programming...  If you think it, it will come...

Seriously though, I have been thinking along the lines of the
common Fortress/Merlin extensions mechanism and Peter's intercepter
concepts.  If Avalon components can have a universally extensible
lifecycle, we can substitute Contextualizable for whatever we want
(like BlockContextualizable).

The ideas are still mulling around in my head, and when I can
formulate a proposal, I will post it to the list.  I will address
the issues of contracts, how we can make the system workable across
containers, and other issues in the proposal.