At 12:31 PM 10/5/2001 +0200, you wrote: >Here I have the feeling we are doing the same mistake over again: the >sitemap was compiled when no hotspot tecnique was present and we had to >avoid excessive use of esternal recurrent logic when we could "unroll" >the tree traversal and let java execute it directly by transforming it >in code.
I think the sitemap is really metadata that configures the cocoon engine. So in that respect are we mixing concerns by converting metadata into program code? I took your previous words about the removal of hotspots and applied those to our XSP pages in house. Before I was recreating the same java code repeatedly. As an answer to the hotspot issue, I moved the code into a separate class file with static methods, just like many of the internal logicsheets. I mention this because maybe we could apply some of the same techniques to the sitemap? Rather than generating a bunch of different methods, etc, could we not just compile the sitemap to a bunch of static variables (metadata) with method calls to do the actual work? Thus gaining some of the benefits of hotspotting? That might provide a migration plan towards a more radical design. It might also be As more and more people come on board using version 2, we need to protect the investment people are making in the current sitemap model. At least from the standpoint of providing a seamless transition to what is next, in both functionality and brain power required to understand. I have been enjoying the recent RT threads though. I do appreciate that such discussions take place out in the openness of the dev list. Of course that is what makes open source software so great :) keep hacking. -pete -- peter royal -> [EMAIL PROTECTED] managing partners, inc. -> http://www.managingpartners.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
