Thank you Ard, That's what I'm looking for I think.
Marcel -----Oorspronkelijk bericht----- Van: Ard Schrijvers [mailto:[EMAIL PROTECTED] Verzonden: maandag 9 januari 2006 14:23 Aan: [email protected] Onderwerp: RE: looking into the cocoon cache Think that you should set the right loggings (the ones you're interested in, like caching, store, janitor) to DEBUG in your logkit.xconf if you want to see generated cache-keys, memory use etc Is that what you're looking for? AS > > > Thank you Ard, > > The status generator generates a lot of information :-s > But I think I can handle it ;-) > > But this still leaves me with the question if it's possible > to see which > cacheable item is used in a pipeline request? > > Thanks, > Marcel > > -----Oorspronkelijk bericht----- > Van: Ard Schrijvers [mailto:[EMAIL PROTECTED] > Verzonden: maandag 9 januari 2006 9:45 > Aan: [email protected] > Onderwerp: RE: looking into the cocoon cache > > I happened to be doing it at the moment :-) > > <map:match pattern="status"> > <map:generate src="status" type="status"/> > <map:serialize type="xml"/> > </map:match> > > AS > > > > Hi, > > Is it possible to look into the cocoon cache, to see what's > in there at > a certain point in time? > And is it also possible to see which cacheable items are used in a > pipeline request? > > I want to use this to check if my caching works correct. > > Thank you, > Marcel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
