cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Lewis <>
Subject RE: cache thoughts
Date Wed, 23 Feb 2000 16:49:02 GMT
My cache needs are similar to your - although I personally would love to see
the ability to allow even dynamic pages from a real-time system be
optionally cache for short period. Something like a cache with a
time-to-live feature.

Andy Lewis
VERITAS Software, Heathrow, Florida
Voice:  407-531-7584  -  Fax:  407-531-7686  -  Cell:  407-718-4718
Pager:  -  EMail:

" Some days, it is best to keep reality at arms length..."

		-----Original Message-----
		From:	Mike Engelhart []
		Sent:	Wednesday, February 23, 2000 11:39 AM
		To:	Cocoon Dev
		Subject:	cache thoughts

		I've been mulling over the cache issue over the last 24
hours and have some
		thoughts i'd like to air out.

		In my particular development instance, I actually don't want
the final
		output page cached because the data is retrieved from a
		transaction system.  That said, what I do think needs to be
cached are the
		style sheets that are used to generate the final output.
Reading in one or
		more stylesheets from disk is always going to be slow
especially if you're
		using includes or imports.  It seems to me that the xalan
processing speed
		is pretty amazing.  All of my pages are completely dynamic
XSP down to the
		localized text being read out of java.util.ResourceBundle's
and my pages are
		relatively quickly (about 2.5-3x slower than a static html
file) including
		reading 2 stylesheets and all the dynamic XSP stuff and the
fact that it's
		running through Apache->JServ->Tomcat->Cocoon and back
out.(Yikes that's a
		mess!!).  I would think that not having to read in the XSL
sheet would
		significantly speed up the process.

		Any thoughts.  If this is a valid assumption is this
something that needs to
		be cached by Cocoon or by xalan?  If it's cocoon, would the
existing cache
		model work well for this?


View raw message