> > I always thought this would be a good thing. Have you implemented it for > > the compiled sitemap, for the treeprocessor or for both? > > Alas, I was too short on time to catch up both with TreeProcessor anc > compiled sitemap, so as of now this is available only on TreeProcessor.
great > I might do my best to reconcile this change and port it to the compiled > sitemap too, but I don't expect this to be an easy task. Besides, I > think this is about time to discuss about this issue and put some rules. > I see these possible choices: aggreed > 1. choose one implementation (be it treeprocessor or compiled) and stick > to it; > 2. keep both, and let developers work with the one they prefer (with > possible out of synch changes); > 3. keep both, but refuse to release components that work only with one > sitemap engine. > > Personally I'd go for 1 and choose treeprocessor, unless there are > benchmarks stating that a compiled sitemap is definitely faster. 3 is > good to, but I'd avoid 2 as hell. I'd go for 1) , too. So maybe we should vote on deprecating the compiled sitemap then... -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
