[Ann] IncrementalSearch 0.1, ManagableIndex 0.10, AdvancedQuery 0.6
"IncrementalSearch" is an efficient incremental search engine supporting 'and', 'or' and 'not' queries. Unlike Zope's standard search engine, it determines hits incrementally, one at a time. It interleaves index lookup and thereby prevents the creation of large intermediate result sets and touches (almost) as few index blocks as possible. This can significantly reduce load time. Measurements comparing an incremental PathIndex with a standard Zope PathIndex showed speedups between 0.8 upto 50. Download: <http://www.dieter.handshake.de/pyprojects/zope#IncrementalSearch> "ManagableIndex" is a flexible indexing framework for the construction of efficient indexes tailorable via the Zope Management Interface. It now comes out of the box with Field-, Keyword-, Range-, Path- and WordIndexes. Unlike other index implementation which support pattern matching only for TextIndex, Managable Field-, Keyword- and WordIndexes support both glob as well as regular expression matching provided the indexed values are strings. New in version 0.10: * it now uses "IncrementalSearch" if available * an improved PathIndex with a new "depth" search option. While "level" controls the distance of the search path from the beginning (as with the standard PathIndex), "depth" controls its distance from the end (in a symmetrical way). * Fixes for unicode values Download: <http://www.dieter.handshake.de/pyprojects/zope#ManagableIndex> "AdvancedQuery" is a Zope product aimed to overcome several limitations of ZCatalog's native search function. Like ZCatalog's search, it supports elementary index searches. While ZCatalog can combine such elementary searches only by "and", AdvancedQuery allows them to be combined arbitrary with & (and), | (or) and ~ (not). While ZCatalog supports an efficient sorting via an index on one level, AdvancedQuery supports sorting via any level of (field) indexes. Moreover, it sorts the result incrementally -- only as far as you access your result. This can drastically speed up the time required for sorting. It uses Python's generators for this (and thus requires Python 2.2 or better). New in version 0.6: it now used "IncrementalSearch" if available. Download: <http://www.dieter.handshake.de/pyprojects/zope#AdvancedQuery> IMPORTANT NOTE: I consider to forbid institutions of the European Union (Commission, Council of Ministers, Parliament, ...) to use software developped by me. This is in protest against plans of the Council of Ministers to make logic (general ideas outside of a concrete technical system) and especially software patentable in Europe. Note that with such a restriction, this software will cease to be compatible with the GPL (GNU Public License). This version does not yet have the restriction but a future version may. -- Dieter
I have been dealing with this problem for awhile, and thought I had a handle on it but apparently not. Once in awhile I will get this returned from my zope sites (many sites, many areas, no pattern) The error was: “bad server response” (NSURLErrorDomain:-1011) It will just display a blank page, no source, nothing. Hit refresh and it will load correctly. I thought it was a zope thread/memory issue but it has started to happen on a newly restarted zope running on 5 threads. Zope 2.7.0b4/CMF1.4x Jake ____________________ http://www.ZopeZone.com "Zoping for the rest of us"
Jake, This does not look like a Zope error to me. What do you have in front of Zope? A Netscape web server? Look there for clues what NSURLErrorDomain:-1011 means. Also note that running 2.0.7b4 is almost certainly not a good idea. What keeps you from running at least 2.7.0 final? Stefan On Aug 26, 2004, at 13:03, Jake wrote:
The error was: “bad server response” (NSURLErrorDomain:-1011)
It will just display a blank page, no source, nothing. Hit refresh and it will load correctly.
I thought it was a zope thread/memory issue but it has started to happen on a newly restarted zope running on 5 threads.
Zope 2.7.0b4/CMF1.4x
-- The time has come to start talking about whether the emperor is as well dressed as we are supposed to think he is. /Pete McBreen/
What keeps me from running 2.7.0 final, was there was a bug in 2.7.0 and 2.7.1 (that is fixed in 2.7.2) that did not work with one of my products. Basically, upgrading a production server, with 7-8 websites is not a small job. Plus, once something is stable and working, and believe me 2.7.0b4 has been the most stable release I have used in 4 years, I like to keep it that way. Right now I am looking to migrate to 2.7.2 w/ CMF 1.5 and Plone 2.04. Jake -- http://www.ZopeZone.com Stefan H. Holek said:
Jake,
This does not look like a Zope error to me. What do you have in front of Zope? A Netscape web server? Look there for clues what NSURLErrorDomain:-1011 means.
Also note that running 2.0.7b4 is almost certainly not a good idea. What keeps you from running at least 2.7.0 final?
Stefan
On Aug 26, 2004, at 13:03, Jake wrote:
The error was: bad server response (NSURLErrorDomain:-1011)
It will just display a blank page, no source, nothing. Hit refresh and it will load correctly.
I thought it was a zope thread/memory issue but it has started to happen on a newly restarted zope running on 5 threads.
Zope 2.7.0b4/CMF1.4x
-- The time has come to start talking about whether the emperor is as well dressed as we are supposed to think he is. /Pete McBreen/
participants (3)
-
Dieter Maurer -
Jake -
Stefan H. Holek