Robert Koberg wrote: >I see from some archives that SM does not like dynamic sitemaps. My tool >needs dynamic sitemaps. > Still a newby, but definitely understanding a bit more about the concepts of cocoon 2, i think are your probably confusing different levels of requirements with regard to change --- or just like me a couple of days ago, not getting to grips completly with the concepts of cocoon 2, what is dynamic and what should'nt be....
The sitemap is "fairly" static by definition, but dynamic by usage ..... With "fairly" i mean: you can change the sitemap, it can grow, it can get smaller etc, but not in the same with the same life-cycle as the content and even structural apperance of your site. The sitemap defines all potential pipelines, aggregations, filters etc.of all possible structural combinations to produce dynamically the content of your site. This surely does not have the same change cycle as content and structural appearance itself, and it can be complex: just like the structure of a structure of a specific sentence of a language versus the structure of the language itself. You can "produce" language in a fairly dynamic and creative way, but the underlying structure, albeit fairly complex, is at any given time static. It evolves also, but very slowly ...... Ok, the comparision does'nt suite all that well, since we are "inventing languages" all the time .... the life - cycle of a site is much shorter than with our "natural" language, there may requirements for managing different overlapping life - cycles of different sitemaps, just like with any code, but that does'nt mean that the sitemap is dynamic. This goes more into the realm of configuration and change management of "code" .... see also the link: http://chello.sourceforge.net/ For early stages of developing complex sites, i also would'nt use cocoon2 that much, but tools with which you can fairly quickly prototype your requirements. After you know more about your requirements, move on to cocoon2, it will help you greatly! If at poiint you have requirements to be able to apply different structural combinations dynamically depending on eg. user preferences etc. That is done generatively by using generators by combining different pipelets (cinclude/xinclude) dynamically , by filtering and/or by aggregation based on the "same" it is "static" sitemap. >Would cocoon be the wrong choice? I mean does the >burden of recompiling the sitemap on each update make it impractical? > Specially if unnecessary ...... > > >thanks, >-Rob > > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> > Christoph Henrici --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
