Hi, *DISCLAIMER* I'm not that sitemape/pipeline guru. From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] > >Vadim Gritsenko wrote: > >> Excellent summary! I will try to address some of your questions below. > >Thanks. I'll try to reply to my best. > >> > - direct -> generator, transformer, serializer, aggregator, reader >> > - indirect -> action >> > - support -> matcher, selector, mount, redirector >> >> From the text below, you are assuming that actions do not perform >> pipeline routing. As of now, they do this, that's why nesting is >> allowed for actions. If action returns not-null map, body of action >> is executed. The question is whether we live it as implemented - then >> action should be moved into "support" group; or actions to be changed. > >Very good point. Changing behavior would ruin back-compatibility, so >let's change the grouping: > > direct -> generate, transform, serialize, aggregate, read > indirect -> act, match, select, mount, redirect > >is this any better? > >> > A pipeline may contain *all* components at the first level. >> > >> > <note who="sm">having 'mount' and 'redirect-to' as first level >> > components doesn't make really sense, but it doesn't hurt either so >> why >> > should we limit it?</note> >> >> I'm for KISS here also; let's drop these artificial limitations. > >Agreed. > >> > <question who="SM">what happens when the client has already received >> > part of the request (say during aggregation?)</question> >> >> The discussion had taken place on this, intermediate output stream was >> suggested to avoid "committed response": >> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99828709211581&w=2 >> and >> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99442091111980&w=2 > >Hmmmm, did you guys thought about using 'chuncked HTTP'?
Could you explain, what do you exactly mean with 'chuncked HTTP'? Gerhard ----------------------------------------------- Consciousness: that annoying time between naps. ----------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
