Re: Context: usage recommendations?

[Leo Sutic]

Adam Murdoch wrote:
> Why do some operations belong in Context and the rest in ServiceManager?
> How is this beneficial enough to the component writer to offset the fact that
> they are forced to locate some operations from one place, and other
> operations from an entirely different place?

Adam,

I understand what you're getting at, and the only answer I have is that there's no definitive answer.

We know that the container can expose services via the context, and via the service manager. Different people do different tradeoffs - for some it was important to make a difference between both, as the container-provided services did not appear in the assembly file, but as some "magic" services available - for other it was more important to have a unified interface. Who was right? I have no idea - I just know that both ways work.

You have yourself drawn up the spectrum of methods, from single-method interfaces, to one-method-for-each-possible-different-case. Where on that spectrum we place Avalon is largely a matter of taste. I know of applications from all over that spectrum that have been built on-time and on-spec. I'm therefore inclined to believe that it does not matter one iota, and that any attempt at formally proving what way is the one true way will by necessity fail and essentially boil down to "because I think so".

There was a framework where the context differed during the life of a component - startup, init, shutdown, etc. had different contexts. Why should they be different?

The same goes for this.

/LS



--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>