Hi Corin,
to be honest, I don't have any plans for this :) Now, I want to make the
tree processor
implementation capable of plugging some profiling things in. That's the
first step.
I'm not sure about excalibur instrument as it isn't maintained anymore as
far as i know.
Carsten
________________________________
From: Corin Moss [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 20, 2004 12:45 PM
To: [EMAIL PROTECTED]
Subject: RE: New Sitemap Treeprocessor for 2.2
Hi Carsten,
Great to hear that you're working on this one. Do you plan to
expose your profiling via the Instrumentation interfaces? I've found the
excalibur instrument tools very useful of late and wonder whether it could
be appropriate to use them here.
Of course, it might not make sense to use them for the type of
profiling you're considering, how were you planning on approaching this part
of it?
Corin
-----Original Message-----
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
Sent: Sat 20/03/2004 10:04 p.m.
To: Cocoon-Dev
Cc:
Subject: FYI: New Sitemap Treeprocessor for 2.2
Hi,
to avoid double efforts in the same area, I just wanted to
inform you that I will try to write a new tree processor
for 2.2 in the next few days.
Why? There are several reasons:
- Reverting to ECM in 2.2 requires some changes to the
tree processor used in 2.1.x anyway
- Implementing Virtual Sitemap Components
- Implementing Inheritance of Views
- Being Container Independent
- Adding a profiling/debugging api
So, apart from reverting to ECM, I will start to implement
some of the new features we planned for 2.2. Please note
that we haven't discussed all points from above in detail
but I think it's easier to discuss on an implementation
base instead of duing endless discussions.
I will try to reuse as much as possible from both tree
processors (2.1 and 2.2). And I hope to come up with
a working solution by the end of next week.
Thanks
Carsten
