On Fri, 25 Jul 2003 14:56:18 -0400, "Tim Olson" <[EMAIL PROTECTED]> said: > thanks, we got a set of sitemaps working.
Great. > it's truly unfortunate that each "fragment" has to be a complete pipeline > with an xml serializer at the tail, because it just gets parsed back into > SAX events for the next pipeline "fragment". this seems like a lot of > unnecessary overhead in a server that's not fast to begin with. When you use a pipeline with the cocoon protocol, the serializer is ignored, so it is reasonably efficient. Regards, Upayavira > > From: Upayavira [mailto:[EMAIL PROTECTED] > > > > On Wed, 23 Jul 2003 10:53:38 -0400, "Tim Olson" > > <[EMAIL PROTECTED]> said: > > > we have a "main" pipeline which handles all requests by firstly > > > performing > > > authentication and lastly performing internationalization, browser > > > tweaking, > > > etc. the middle part of the pipeline is different per page > > so we wanted > > > to > > > organize things with a subsitemap per page (easiest maintenance). > > > however, > > > calling resources between two sitemaps doesn't seem to work (2.0.4, > > > interpreted sitemaps). > > > > > > how can we have a global pipeline which calls out to > > subsitemaps for the > > > middle section of the pipeline? > > > > You could split your pipeline into three parts, the start is > > in your main > > pipeline, and is internal only. Your subsitemap accesses this > > using the > > cocoon: protocol in the second part. Then, back in the main > > sitemap, you > > have the final part of your pipeline, which accesses the > > second part with > > the cocoon: protocol, but can dynamically select which > > subsitemap to use > > by using a URL matcher parameter (e.g. {1}). > > > > Make sense? If you want I can send an example. > > > > Regards, Upayavira > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
