On Thu, 5 Dec 2002 09:38 pm, Peter Donald wrote: > On Thu, 5 Dec 2002 13:48, Adam Murdoch wrote: > > One problem is that it doesn't take long before you hit avalon's enormous > > scope. It's difficult (impossible?) to come up with a useful set of > > mandatory services that will span this scope. Even the canonical > > getHomeDir() example is a problem for lightweight containers with no such > > concept, or tightly sandboxed containers that don't (or can't) allow file > > system access. > > The one common one is getName().
Do you think it would be useful for framwork to include a set of container-independent interfaces that cover some of the common ways that a component interacts with the container? They wouldn't cover every possible interaction - that can remain container-dependent - but just the usual cases. Something more concrete than get(). > > Honestly, MailetContext and ServletContext were always just noise. > > There's nothing in common between these and framework's Context except > > the word 'Context' in their names, and the fact that they each deliver a > > subset of the resources used by components. > > I dunno. They are precisely the sort of things I draw on when thinking > about it :) Fair enough. Can you expand on this? How do you view MailetContext and ServletContext and EntityContext and friends in relation to Context and framework? -- Adam -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
