I was wondering about 2.1 vs 2.0 stuff:
Does the IMAP bug that starts pounding the database server with
similar queries also happen in 2.1 CVS?
I haven't seen it in 2.1 code yet. But then, that code is not as widely used.
I've been trying to get my
head round the bug, looking through all code called by _ic_fetch()..
and it just makes me wanna cry, get a new job, move to a faraway land
without any computers etc. In short, it doesn't make me happy at all.
Well, I didn't think the looping bug was related to _ic_fetch. It always occurs in perform_imap_search afaik.
What makes you think _ic_fetch is involved?
The 2.1 code is a much better piece of engineering, and if it does not
have this bug, it makes sense to move to the new code quickly. It
seems pretty useless to fix the 2.0 IMAP code if we'll abandon it
shortly anyway.
Sorry to disagree here. Even though maintaining two branches with just the three of us seems like overkill,
that is what we agreed on. 2.0 needs to be fixed. I don't need the added pressure of fixing bugs in the
inherently unstable 2.1 code when people start using that codebase for critical deployments. Not, that is,
until we are ready for 2.2.
I can deal with people complaining about lack of features or performance wrt 2.0, but this specific bug is a
project killer.
If only I had a way to reliably reproduce this bug....
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
