Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)

Chris McDonough wrote: > > It just occurred to me that depending on the splitter to do > positions makes it impossible to alter the splitter without > reindexing the whole text index... but I think this is a > reasonable tradeoff. Other opinions welcome. > This raises the question how depend

Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)

> > > Once you're satisfied with the implementation, would you be willing > > submit the module to the collector? > > Do you think you (or someone else for that matter) could have a look at > [1] the method that returns the position in the document - positionInDoc() > - to how that could be made

Re: [Zope-dev] DCOracle2 Beta 3

On Saturday, June 16, 2001, at 08:41 PM, Andreas Repp wrote: > (quoting himself) >> ... To solve the performance problem I´d suggest to cache the user >> connections for a certain period of time. ... > > Of course I haven't meant to 'cache' the connections but to keep em > alive > while the resp

[Zope-dev] SI prefixes and Zope

Hi, I suggest to make Zope prefixes of object sizes be consistent with SI binary prefixes - see http://physics.nist.gov/cuu/Units/binary.html Using SI binary prefixes for object size will avoid any misunderstanding of real object size. Petr -- Petr Knápek Network Development NEXTRA Czech Rep

Re: [Zope-dev] dtml-in batching improved

On Wed, Jun 13, 2001 at 04:28:12PM -0700, Jean Lagarde wrote: > Good day all, > > > Here is the original code, with my annotated change (I deleted an if test in > two places): > > for index in range(first,end): > # preset > kw['previous-s

Re: [Zope-dev] what transaction does get_transaction().commit() really commit?

Jephte Clain wrote: > the question is: what transaction is commited with > get_transaction().commit() ? It is only the one associated > with the connection, or also the transaction in which is the > caller? > I mean, if my method is called from within Zope, is the > transaction of the caller commi

[Zope-dev] Zope/z2 security issues

Hi All, We're currently working on some security issues when running zope in a INSTANCE_HOME (multiple instances running as different users) setup. The first issue is tightening of the current security. We introduced the ability to set the groupid under which the server runs, so you can put zope

Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)

On Sun, 17 Jun 2001, Chris McDonough wrote: > index_object, because the splitter return has all the words > in order, even the dupes... as you iterate, you can mutate Is this part of the current formal Splitter Interface? If not, it needs to be if other code is going to depend on it. Oh, yeah, a

[Zope-dev] replicating storages

We are considering storing some mission-critical data inside a ZODB, but are worried about data loss if the ZEO server should be destroyed. Has anyone looked at solving this problem? Replicated-ZEO looks like it will eventually be ideal solution; the use case is documented at

Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)

The Splitter interface is not really document. However Zope 2.4 has a much better support for 3rd party splitters. Andreas - Original Message - From: "R. David Murray " <[EMAIL PROTECTED]> To: "Chris McDonough" <[EMAIL PROTECTED]> Cc: "Erik Enge" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> S

[Zope-dev] Proposed proposals: password encryption, ZODB RAM

Here are a couple of ideas I'd like to toss out. Proposals can take a lot of time to write and it might be easier this way to flesh out the details. 1) Optional password encryption. Right now passwords are stored as clear text. What's interesting is that Zope can already authenticate again

[Zope-dev] batching badly

Hi, First, I don't post to this list normally; is it the best place to discuss an apparent bug? Anyway, the lowdown: If you iterate over a list with a batch size of 1, it messes up towards the end of the sequence. For example, the following code: calling

Re: [Zope-dev] batching badly

No it's not a bug(in code) but a feature. May You call it a bug (in usability), though. What causes it is that the orphan value defaults to 3 when not explicitely set. See the online help for in tag. LEE Kwan Soo ¢—ƒzùšŠYb²Öh¥àÞ¿:)zŠà†Ûiÿùb²Û3¢—¨®æj)fjåŠËbú?Ί^uëÍ¡Êè²Êh²Û(¬tÌ-éܡا

Re: [Zope-dev] batching badly

> That's not the behaviour I'd expect. Can anyone confirm this is a > bug? As LEE Kwan Soo has already said, it is not a bug, but a clever (too clever?) feature that should maybe not be enabled by default. Every second week or so somebody runs into this and thinks it is a bug. To the DC people:

Re: [Zope-dev] Proposed proposals: password encryption, ZODB RAM

On Mon, Jun 18, 2001 at 12:28:54PM -0400, Shane Hathaway wrote: > 1) Optional password encryption. Right now passwords are stored as > clear text. What's interesting is that Zope can already authenticate > against SHA encrypted passwords, it just won't encrypt user passwords > unless you forc

Re: [Zope-dev] Where did DocumentTemplate/VSEval.py go in 2.4.0a1?

Michel Pelletier wrote: > Should we make an alias for bw-compatability? This is now in the trunk, along with some other compatibility changes that allow Python Methods to continue working, courtesy of the NewZopeOrg migration project. Cheers, Evan @ digicool ___

Re: [Zope-dev] batching badly

Joachim Werner wrote: > > > That's not the behaviour I'd expect. Can anyone confirm this is a > > bug? > > As LEE Kwan Soo has already said, it is not a bug, but a clever (too > clever?) feature that should maybe not be enabled by default. Every second > week or so somebody runs into this and t

Re: [Zope-dev] Proposed proposals: password encryption, ZODB RAM

On Monday 18 June 2001 15:33, Martijn Pieters wrote: > On Mon, Jun 18, 2001 at 12:28:54PM -0400, Shane Hathaway wrote: > > 1) Optional password encryption. Right now passwords are stored as > > clear text. What's interesting is that Zope can already authenticate > > against SHA encrypted passwor

Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)

Rik Hoekstra writes: > This raises the question how dependent the splitter on the paticularities of the > document source - I do not really see how different splitters could be useful > for one single document. This is perhaps less obvious than it appears, as you > may want to use different sp

[Zope-dev] better history diff output ?

Hi all, I want to highlight a wiki page's last changes, so I have a need for a better display of diffs between two revisions. Can you recommend any good free diff code out there with nice html output ? ___ Zope-Dev maillist - [EMAIL PROTECTED] http

Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)

These are good ideas to improve the TextIndex. I already encouraged Erik to put alltogether into a Fishbowl proposal, Andreas - Original Message - From: "Dieter Maurer" <[EMAIL PROTECTED]> To: "Rik Hoekstra" <[EMAIL PROTECTED]> Cc: "Chris McDonough" <[EMAIL PROTECTED]>; "Erik Enge" <[EMAI

[Zope-dev] Re: better history diff output ?

PS, you can see my brief version of history's ndiff-based output at eg http://zwiki.org/FrontPage/diff . I hid the unchanged sections and tweaked the table layout. (My lasttext, diff, dump, & replace routines are at http://zwiki.org/ZWikiPagePy or http://zwiki.org/zwikidir/ZWikiPage.py ) __

[Zope-dev] decapitate() still needed ?

from http://zwiki.org/FrontPage: > simon - why is the antidecaptiation kludge there? > > tav - it was a temporary way around an undocumented feature of DTML > Documents, namely if your document's text begins with one or more > lines that look like a http: header, they get moved into the actual >