On 3/6/07, Dieter Maurer [EMAIL PROTECTED] wrote:
Lennart Regebro wrote at 2007-2-23 21:25 +0100:
...
Compared with Lucene for example, which instead will create iterators
who will only resturn the next match. This saves you from a lot of
index searching when you have big results.
I don't know
Roché Compaan wrote at 2007-2-25 11:48 +0200:
...
I see several problems:
* the RAMCacheManager does not provide an API to implement
this policy
* a cache manager would need a special data structure
to efficiently implement the policy (given a documentId,
find all
Lennart Regebro wrote at 2007-2-23 21:25 +0100:
...
Compared with Lucene for example, which instead will create iterators
who will only resturn the next match. This saves you from a lot of
index searching when you have big results.
I don't know if it is feasible to do something like that, but it
On Sat, 2007-02-24 at 09:48 +0100, Dieter Maurer wrote:
Roché Compaan wrote at 2007-2-23 22:00 +0200:
...
Thanks for that pointer. It's good that way, it should make invalidation
easier. It could be as simple as invalidating any cached result that
contains the documentId being indexed. Do
On Fri, 2007-02-23 at 21:25 +0100, Lennart Regebro wrote:
On 2/23/07, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
It may require a bit of hacking the catalog, of course. Perhaps it's
time to start thinking about componentizing the Zope 2 catalog to make
such things easier in the
Roché Compaan wrote at 2007-2-23 22:00 +0200:
...
Thanks for that pointer. It's good that way, it should make invalidation
easier. It could be as simple as invalidating any cached result that
contains the documentId being indexed. Do you see any problem with the
following invalidation strategy:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roché Compaan wrote:
I'm curious, has anybody played around with the idea of caching ZCatalog
results and if I submitted a patch to do this would it be excepted?
I quickly coded some basic caching of results on a volatile attribute
and I was
On Fri, 2007-02-23 at 06:55 -0500, Tres Seaver wrote:
Roché Compaan wrote:
I'm curious, has anybody played around with the idea of caching ZCatalog
results and if I submitted a patch to do this would it be excepted?
I quickly coded some basic caching of results on a volatile attribute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roché Compaan wrote:
On Fri, 2007-02-23 at 06:55 -0500, Tres Seaver wrote:
Roché Compaan wrote:
I'm curious, has anybody played around with the idea of caching ZCatalog
results and if I submitted a patch to do this would it be excepted?
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Roché Compaan wrote:
On Fri, 2007-02-23 at 06:55 -0500, Tres Seaver wrote:
Roché Compaan wrote:
I'm curious, has anybody played around with the idea of caching ZCatalog
results and if I submitted a patch to do this would it be
On Fri, 2007-02-23 at 12:09 -0500, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Roché Compaan wrote:
On Fri, 2007-02-23 at 06:55 -0500, Tres Seaver wrote:
Roché Compaan wrote:
I'm curious, has anybody played around with the idea of caching
Tres Seaver wrote:
Tres Seaver wrote:
Roché Compaan wrote:
On Fri, 2007-02-23 at 06:55 -0500, Tres Seaver wrote:
Roché Compaan wrote:
I'm curious, has anybody played around with the idea of caching ZCatalog
results and if I submitted a patch to do this would it be excepted?
I quickly coded
Roché Compaan wrote at 2007-2-23 18:44 +0200:
...
Cool idea. I haven't done any coding involving OFS.Cache though. Looking
at it briefly it looks like one can modify the catalog to subclass
OFS.Cacheable and then use the ZCacheable_get, ZCacheable_set and
ZCacheable_invalidate methods to interact
On Fri, 2007-02-23 at 20:43 +0100, Dieter Maurer wrote:
Roché Compaan wrote at 2007-2-23 18:44 +0200:
...
Cool idea. I haven't done any coding involving OFS.Cache though. Looking
at it briefly it looks like one can modify the catalog to subclass
OFS.Cacheable and then use the ZCacheable_get,
On 2/23/07, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
It may require a bit of hacking the catalog, of course. Perhaps it's
time to start thinking about componentizing the Zope 2 catalog to make
such things easier in the future?
Yup. It would also be interesting to look into making it
15 matches
Mail list logo
