Dear cocooners,

Here is first try to implement profiler, checked in into HEAD branch. To use:

1) Configure cocoon.xconf:

  <event-pipeline 
class="org.apache.cocoon.components.profiler.ProfilingNonCachingEventPipeline"/>
  <sax-connector class="org.apache.cocoon.components.profiler.ProfilingSAXConnector"/>
  <profiler/>

2) Configure sitemap:

  <map:generators default="file">
   ...
   <map:generator  name="profile"     
src="org.apache.cocoon.components.profiler.ProfilerGenerator" label="content"/>
  </map:generators>
  ...

   <map:match pattern="profile">
    <map:generate type="profile"/>
    <map:transform type="xslt" src="stylesheets/system/profile2html.xsl"/>
    <map:serialize/>
   </map:match>

3) Try http://localhost/cocoon/profile several times

Feedback is really appreciated,

Thanks,
Vadim

> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 05, 2001 10:36
> To: [EMAIL PROTECTED]
> Subject: Re: Profiler for C2
> 
> 
> Vadim Gritsenko wrote:
> > 
> > Berin,
> > 
> > One question though...
> > 
> > It constists from:
> >  - central profiler component,
> >  - sax connector,
> >  - extended event pipeline,
> >  - profiler generator,
> >  - and one stylesheet to present results :)
> > 
> > Shall I put everything in one package (**.cocoon.profiler), or split
> > across packages (**.generation, **.pipeline, **.saxconnector)?
> > 
> > PS: some actions should be added later to control profiler
> 
> If there are a number of components to the one solution, it would probably
> be better to place them in "org.apache.cocoon.components.profiler" than
> spreading them throughout the other packages.  It is somewhat of a special
> case.
> 
> > 
> > Vadim
> > 
> > > -----Original Message-----
> > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, July 05, 2001 9:30
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: Profiler for C2
> > >
> > >
> > > Vadim Gritsenko wrote:
> > > >
> > > > Hello,
> > > >
> > > > I do have something which looks like and performs like a profiler :)
> > > > It can report time spent by every step of pipeline; it's built using
> > > > SAXConnector. Is there anybody here interested in this?
> > >
> > > Sure.  Commit it to the 2.1 branch, and we can vote to include it in
> > > the 2.0 branch.
> > >
> > > >
> > > > If yes, shall I commit it to CVS? (what branch?)
> > > > Or, I can post it to mail list.
> > > >
> > > > Regards,
> > > > Vadim
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, email: [EMAIL PROTECTED]
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to