on Mon, 01 Sep 2003 13:37:20 -0700 Miles Elam <[EMAIL PROTECTED]> wrote:
> Also, something like > > <map:aggregate> > <map:generate type="file" src="foo.xml"/> > <map:generate type="directory" src="foo/"/> > <map:generate type="custom" src="bar"/> > </map:aggregate> > > looks a bit odd to me. Then again, that may simply be because I'm not > used to it. It would definitely require some retooling of the > pipeline code to accommodate. This looks odd, but think os using two generators of the same type used on different source or used on the same source but with different parameters; aggregator's params allow you to make output looking like directly from generator. > <whatever/> > > It just so happens that the developers have been talking about doing > away with resources in favor of pipeline fragments. The thread > appears to be missing(!?!) on marc.theaimsgroup.com. However, in the > real-time.com archives, you can find Stefano's proposal and resulting > thread of discussion > (http://archives.real-time.com/pipermail/cocoon-devel/2003-August/018 > 386.html). Couldn't open the url nor find the result (big tree thread), but after reading the first paragraph of the Stefano's proposal I think VPC could resolve problems I mentioned. > But the same point applies to aggegated generators too I guess. Virtual Pipeline Componets + aggregator taking any generator would made aggregating resources problem nonexisted. <BTW about="map:resource"> map:resource really looks like map:match with literal pattern (no special chars) that ends with xml serializer and is putted in internal pipeline, ie. resource looks like pipeline part and AFAIR docs doesn't say it's not. Considering this, map:resource looks like component intended for sitemap modularisation, and internal pipelines looks like workaround for use with aggregators. IMO simplest workaround for this would be special protocol for map:resources (probably outdated by virtual pipeline components). </BTW> I think that's all. Regards, Rufio -- nmap -sS -O -p80,81 www.microsoft.com [..] Running: Linux 2.5.X OS details: Linux Kernel 2.4.18 - 2.5.70 (X86) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
