Hi,

On May 5, 2008, at 22:23 , Fabrizio Giustina wrote:

On Wed, Apr 30, 2008 at 7:37 PM, Grégory Joseph <dev- [EMAIL PROTECTED]> wrote:
After multiple cache issues we've had on various projects, we've decided to give it a quick rewrite to try and solve some of the problems we've had.

nice :)

We recently used the current ehcache based implementation on a site
with an high traffic (> 1M page view/day) and very dinamic pages,
tweaking it in order to cache all the most accessed documents in
memory for a short timeframe, and this worked very very well...
anyway, we also was facing some limitations due to the legacy cache
module implementation and started to think about a few
enhancement/modifications.


I still haven't check your code but there are a couple of thoughts
that I think I could work at:

- different compression methods: we currently only support gzip, but
we should be able to apply different compression methods and maybe to
chain them. We added a javascript compression based on Dojo ShrinkSafe
that gives a real boost to ajax-intensive websites, I think this could
be added by default to the cache module (we also tested a css
compressor that can be added, although it didn't looked so useful as
the javascript compressor).

Good idea - had not thought about this - although given the following, it should be very easy:

- decouple compression from caching: actually we can gzip only content
that it's cached.

Done - it's a separate filter now :)

But what about gzipping content (e.g. css) without
caching it?

info.magnolia.module.cache.filter.StandaloneGZipFilter :)

Or reuse the same compression with different cache
implementations?

You can have multiple cache configurations, and multiple instance of the cache filter, each refering to its own cache configuration by name.

- ability to configure cache regions: e.g. pages that need to be
cached for a long time in filesystem and resources that needs to be
kept in memory.

As above - multiple cache configs are possible.

It would be nice if a new cache module implementation could be ready
for those features (at least providing a way to plug them in)... did
you had any similar requirement/thought? Do anybody have any objection
if I start pushing those things in? :)

Please check what's in now - and let's discuss before starting more work - I don't consider the api stable or finalized just yet.

One thing that'd interest me specifically is some feedback on your ehcache configuration tweaks, and how it behaved with large documents.

Cheers,

-greg


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to