Leo Simons wrote:
>>I have been inspired by some comments by Igor over in Phoenix land. Now I
>>think ALL of our containers are too primitive, too hard and too inflexible.
>>In a year they will all be considered obsolete, archaic remains.
>>
>>Those ideas I was trying to figure out in containerkit (and previously in
>>atlantis/camelot) are all WRONG WRONG WRONG. I have seen a very very very
>>nice future and it is when everything is written using interceptors.
Interceptors, MVC, Model 12345, etc, buzzwords IMHO.
I have seen interceptors being used, and I also have seen many
implementations as hacks.
You cannot easily control what happens when you put various layers of
interception in your calls, and it can lead to lack of control.
This in general, but maybe you have The Right Way...
> Could be nice...my feeling is that in two years, that will again be
> obsolete 'cause everything will be written using SEDA/Silk-like stuff. I
> had the feeling a long time ago when first playing around with the
> Commandable stuff (ie observer/command pattern).
And I have the same feeling too...
The point is: what does interception give us that lifecycle extension
cannot?
Lifecycle is the *key* to Avalon use and comprehension, and it has
remained solid in time, where other features have not always.
Peter Donald wrote:
"
For example a component C1, may expose services S1 and S2. When a call
is made on S1 from component C2 then Interceptor chain I1 is used, while
if C2 made a call on S2 then chain I2 is used. If another component C3
made a call on S1 then I3 may be used.
As you can see this gets very complex, very fast. Because of this we
need to define a simple, yet sufficiently capable enough configuration
format for these interceptr chains. (If this is even possible).
"
Interceptors are nice conceptually, but must be yet tested in Avalon
with regards to extensions.
> We'll see.....
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
