On Tue, 2002-09-17 at 14:44, Berin Loritsch wrote: > 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. > > > > > > 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). > > > > We'll see..... > > > Not everything. It is a different component model completely. SEDA > would not be a good fit for Cocoon because you cannot work on a partial > document at a time.
=) My bet is that the things you would solve in cocoon using interceptors you could better solve with an event model...of course you can't make everything into events, but you can't make everything into interceptors either (or you end up in dynamic hell). > It works best when you can assemble a document > model piece by piece, or even better process it directly in the stream. SAX is basically event-based, isn't it =) it is just that SAX guarantees a certain order to events. (ie precisely follows the XML file it reads). I can't see why you cannot make guarantees like that in SEDA-like systems. oh well, this is distant-future stuff....interceptors have been around a lot longer =) - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
