> On Fri, 9 Nov 2001 08:59:34 -0500,
> Lawrence Greenfield <[EMAIL PROTECTED]> (lg) writes:
lg> If we're going to worry about Sieve performance, we really should look
lg> into compiling scripts to a byte-code. Currently we run lex/yacc on a
lg> script on _every delivery_. This is pretty
From: Amos Gouaux <[EMAIL PROTECTED]>
Date: Fri, 09 Nov 2001 00:15:07 -0600
[...]
What about all the stats looking for the script? Could that be a
problem? If so, could a db be used as a Sieve script index, like
the mailboxes.db?
If we're going to worry about Sieve performance,
On Fri, 2001-11-09 at 06:15, Amos Gouaux wrote:
> What about all the stats looking for the script? Could that be a
> problem? If so, could a db be used as a Sieve script index, like
> the mailboxes.db?
>
That would be a possible optimisation. Currently, the is one fopen call
for every deliver
> On 08 Nov 2001 18:22:35 +,
> Ian Castle <[EMAIL PROTECTED]> (ic) writes:
ic> 8. Summary
ic> I think this is a good solution because:
ic> - No new concepts are introduced, it is rather a clarification of
ic> existing ones
ic> - Backwards compatibility is preserved
ic> - You get som
This follows on from my previous email, where I presented a method of
enabling sieving on mail delivered directly to shared/public folders.
While that does all the I need it to do, my implementation only allowed
a single active script for all public folders. This is a serious
limitation if you wa
