Hi,

I've missed a big part of the discussion but I have some thought and questions over it:

1) AxKit::Cache is just fine for the cache needs and really a lot of thigs come for 
free. I wonder when/if the last changes that were made to the cache API will get into 
a release.

2) The cache mechanism itself should be really trivial but the main problem for me is 
how the cache will be controlled. Because it is all dynamic you cannot easily say when 
the cache for a certain page should be updated. I was thinking to base the cache on 
namespaces and if for example we have a "news" taglib whenever we call <news:update/> 
we get all subsequent files with the "news" taglib defined in them updated. The only 
problem here is that you need to share this info between the apache processes (the 
update function is called in only one process and the cache should be updated in all) 
which is a bit unpleasant - so far none of the AxKit components does this and you have 
to add new stuff for IPC that is most of the time dependant on other CPAN modules. Is 
there a workaround for this that I've missed? Do you have a more elegant ideas than an 
namespace based cache?

I was thinking for some time already to start building this and I was about to start 
when the discussion of the changed cache API came out.

Pavel



  ----- Original Message ----- 
  From: Matt Sergeant 
  To: [EMAIL PROTECTED] 
  Cc: [EMAIL PROTECTED] 
  Sent: Monday, March 31, 2003 9:50 AM
  Subject: Re: [RFC] Taglib Output Caching


  On Sunday, Mar 30, 2003, at 23:54 Europe/London, Christopher H. Laco  
  wrote:

  > After looking at
  > http://search.cpan.org/src/MSERGEANT/AxKit-1.6.1/lib/Apache/AxKit/ 
  > Cache.pm
  > , all see (aka, understand) is file-based caching.

  The AxKit cache mechanism is overridable using standard AxKit config  
  directives. Many people build their own cache class that implements the  
  same API but stores the cache elsewhere. I'm just trying to say don't  
  reinvent this wheel.

  Matt.


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



Reply via email to