On Tue, Jun 07, 2005 at 08:12:13PM +0200, Mieke Banderas wrote: : What should I look for if I want a simplistic system for avoiding trips : to the DB for pages that are only built upon and between changes are 100% : similar? Is there a cache framework I should look into or could I use : something even simpler? After all, most pages only occasionally have true : dynamic needs. I suppose I'm looking for something like a publishing : system, only much much simpler, especially on how much resources (and : coding) it would need.
So are you looking to cache *pages* (generated HTML content) or simply *data* (information pulled from the DB that is manipulated by the presentation layer)? For the former, there are ways to make the Apache httpd a content caching engine. This works well if the content you'd like cached is global -- that is, not tied to a specific user or group login. (You could also use webDAV for this._ For the latter, you could roll your own persistence caching framework or look into something such as IBatis or Hibernate that will do the grunt work for you. If your code has uniform, centralized, abstracted data access then slipping in another layer between your app and the database shouldn't require much in the way of noticeable changes. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
