This sounds awesome! I'm really looking forward to it. Are there any
drawbacks to this solution?
Thanks, it was originally an idea from Andi/ Morgen/ Brian (Kirsch?) as
far as I know, so they should get the credit :)
Probably the biggest drawback is that we'll have this IMAP server
running in the background. It actually shouldn't be too much of a
performance hit since we'll generally only have one client connecting to
it, but it is something to think about.
Related, but important, is the fact that we convert messages from
Chandler Items to another kind of Python object on the fly to work with
Twisted's interfaces., and on a larger scale this could be annoying
performance-wise. Fortunately, I think there may be an elegant way
around it in tweaking the way Chandler handles MIME support.
Also, as per Mimi's e-mail, some of the workflow issues could get kind
of complicated. There are probably some novel solutions to this,
however, and I'm going to start looking into them today, I think.
-Travis
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
