Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
On 16 Dec 2003, at 14:02, bernhard huber wrote:
hi,
snip/
Now, the way the event cache works is like this:
a) a cache validity is generated
b) pipeline is executed
c) result is stored in the cache
then the pipeline is never called, until an
Hunsberger, Peter wrote:
Sylvain Wallez [EMAIL PROTECTED] writes:
We're talking about validities, but before checking a validity, we first have to obtain it through the cache key.
In the current Cocoon architecture, keys of cache entries are built with abitrary data defined by each of the
Sylvain Wallez [EMAIL PROTECTED] asks:
That's sort of one of the things that we are doing, only within the
current Cocoon infrastructure: in some places we maintain
our own static hash map of key strings that map to Cocoon
validities. We can the look up a Cocoon validity and have it
On 18 Dec 2003, at 05:27, Sylvain Wallez wrote:
We're talking about validities, but before checking a validity, we
first have to obtain it through the cache key.
In the current Cocoon architecture, keys of cache entries are built
with abitrary data defined by each of the individual pipeline
Stefano Mazzocchi wrote:
On 16 Dec 2003, at 14:02, bernhard huber wrote:
hi,
snip/
Now, the way the event cache works is like this:
a) a cache validity is generated
b) pipeline is executed
c) result is stored in the cache
then the pipeline is never called, until an event is triggered
Sylvain Wallez [EMAIL PROTECTED] writes:
We're talking about validities, but before checking a
validity, we first
have to obtain it through the cache key.
In the current Cocoon architecture, keys of cache entries are
built with
abitrary data defined by each of the individual pipeline
On 16 Dec 2003, at 11:09, Hunsberger, Peter wrote:
Stefano Mazzocchi [EMAIL PROTECTED] writes:
Now, the problem is: if I am not the one who generates the
validity (in
linotype, it's the directory generator), how can I invalidate it? how
can I have access to it?
We use data classes that generate
On 16 Dec 2003, at 14:02, bernhard huber wrote:
hi,
snip/
Now, the way the event cache works is like this:
a) a cache validity is generated
b) pipeline is executed
c) result is stored in the cache
then the pipeline is never called, until an event is triggered
externally (from an avalon
After lots of thinking, I came to the conclusion that the only way of
doing serious caching is using the inverted cache approach, which is
prototyped in the eventcache block.
My problem is that linotype is too slow for the load that my blog
generates and runs at 98% of server CPU. The reason
Stefano Mazzocchi wrote:
Now, the way the event cache works is like this:
a) a cache validity is generated
b) pipeline is executed
c) result is stored in the cache
then the pipeline is never called, until an event is triggered
externally (from an avalon component) that invalidates that
Stefano Mazzocchi wrote:
After lots of thinking, I came to the conclusion that the
only way of doing serious caching is using the inverted
cache approach, which is prototyped in the eventcache block.
My problem is that linotype is too slow for the load that my
blog generates and
Christian Haul wrote:
Stefano Mazzocchi wrote:
Now, the way the event cache works is like this:
a) a cache validity is generated
b) pipeline is executed
c) result is stored in the cache
then the pipeline is never called, until an event is triggered
externally (from
Unico Hommes wrote:
Christian Haul wrote:
Still, there is a problem to solve: Which is the right point
for the decision to use the cache?
Will the pipeline be
assembled and all components have their setup method called
or is the validity checked first?
Should actions and
selectors execute?
Stefano Mazzocchi [EMAIL PROTECTED] writes:
After lots of thinking, I came to the conclusion that the only way of
doing serious caching is using the inverted cache approach,
which is
prototyped in the eventcache block.
Well, I don't know if it's the only way, but for anything driven out
hi,
snip/
Now, the way the event cache works is like this:
a) a cache validity is generated
b) pipeline is executed
c) result is stored in the cache
then the pipeline is never called, until an event is triggered
externally (from an avalon component) that invalidates that
Geoff Howard wrote:
Now, one problem I never solved related to the file system specifically
was how to do what I thought of as wild card events. In a file
system, if your validity is built on /dir/to/your/files/myFile.xml and
you delete the entire /dir/to directory tree how do you fire that
16 matches
Mail list logo
