[Twisted-Python] twisted.protocols.imap4

Anders Hammarquist iko at cd.chalmers.se
Thu Jun 12 11:56:19 EDT 2003


I've started looking at the imap4 server implementation in twisted as
I need it for a project. Before I rip it apart completely to fix the
things I think need fixing, I thought I'd air my complaints and ask if
there was a particular reason things are the way they are. 

First of all, I don't understand why UID message references are
handled they way they are. As I understand it, bit operations on the
message number are used to determine if a particular message number
is a UID or a sequential message number. To me, this looks like an
attempt to optimise something which probably doesn't need it. Anyone
care to comment?

Two, the way the message numbers are parsed (whether UID or not),
result in SERIOUS preformance issues for a message range of the
form 1:*. I feel the message number parser needs to know what
messages are available, which needs some restructuring of the mailbox

Three, the obligatory patch. Empty strings need to be quoted in


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/x-patch
Size: 533 bytes
Desc: not available
Url : http://twistedmatrix.com/pipermail/twisted-python/attachments/20030612/f4b5c5c2/attachment.bin 
-------------- next part --------------
 -- Of course I'm crazy, but that doesn't mean I'm wrong.
Anders Hammarquist                                  | iko at cd.chalmers.se
Physics student, Chalmers University of Technology, | Hem: +46 31 88 48 50
G|teborg, Sweden.           RADIO: SM6XMM and N2JGL | Mob: +46 707 27 86 87

More information about the Twisted-Python mailing list