Stefano Bagnara wrote:
IIRC current IMAP support does not persist messages.
This is a blocking issue. We can add it when it is at least working (also
with limits).
This is good. What's involved in persisting the IMAP
messages? Why is persisting IMAP messages different
than persisting POP messages? Shouldn't they be
writing to the same store object and/or database?
Hopefully we can document the remaining issues
and requirements necessary for getting preliminary
IMAP support in.
I don't understand what is the Foedus License. Do you know that?
Yeah, he doesn't seem to have it anywhere on the site.
I emailed him, he said we can treat it as public domain.
I don't know much of our experimental IMAP but it seems to me that our imap
is more advanced than the code inside foedus.
But James has a large learning curve, and there is
the question of whether the changes are even going
to get into the tree. An IMAP authorative IMAP
roadmap is really needed if that is to be done.
I've seen many developers asking for the status in this list, maybe there is
only needs for a lead.
I agree. I think that's the case. If very basic
IMAP support goes in as experimental. I suspect
adoptors would eventually, over time, add the
important missing pieces.
Regards,
Kervin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
