> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > > > Even better would be to start migrating to Fortress. > > All your expensive stuff on the backend is done asyncronously, > > so the critical path is not affected. > > > > Another one would be to fix the assumption that lookup/release > > is 0 time. That is obviously proven false in this case. > > > > The fact that the cache has to lookup and release up to 15 > > components at runtime is horrendous. That makes me think > > that the cache should be redesigned so that it is self contained. > > Berin, > > Not cache. Cocoon engine: > > 1. Cocoon lookups sitemap processor. > 2. Processor (sitemap) lookups pipelines. > 3. Sitemap selects all matchers, selectors, actions, generators, > serializers, transformers as needed (you have to build pipeline). > 4. Pipeline [gets cached response and] lookups XML deserializer. > > The more complex sitemap you have (more matchers/selectors/etc), the > more lookups will happen. Say, every cocoon source will > lookup processor > and continue the process from step 2.
I see. I misread your post. > <flame-bait> > I know that you want to use pre-built pipelines, but (skipping > discussion of how this could be possible) with growing site complexity > amount of all possible pipelines in the sitemap grows exponentially > (IIRC, DNA has only four building blocks, but amount of possible > combinations is close to infinity), thus making any effort to > pre-built > pipelines ahead of time futile. > </flame-bait> > > ;) I wasn't addressing that at the moment. Fortress will help tremendously. We just need a RoleManager that can read the old style of XXXX.roles file, and a Fortress Container decendant that can read the old style of XXXX.xconf files. They are very similar, and Fortress is really what you guys need. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
