On Nov 10, 2003, Danny Angus wrote:
Zoe, (Beware, long answer!)
Thanks for the explanations :)
Ist point.. James IMAP component is very much alpha status *still* .
Oh, well... that would make only three incomplete IMAP implementations I know of: James, JimapD and Foedus. Do I see a trend here ;)
[snip rational]
So.. What is the answer for ZOE...
Well my impression of James is that I think that it would be foolhardy to
take James' alpha IMAP and try to rewrite it with no reference to James,
Avalon or Mailet and I think it would be exceedingly tortuous (but not
necessarily impossible) to implement an IMAP server using JavaMail.
I'm going to find out very soon as a solution stumbled upon me: a lightweight, IMAP SDK build in terms of the JavaMail API. With such a toolkit, one only needs to provide its own implementation of a javax.mail.Store to the SDK. The SDK handles all the IMAP protocol minutia and interact with the underlying data through the Store, Folder and Message API. All this in a small package and no other dependencies than JavaMail :)
It might be worth looking at Avalon Phoenix or Merlin and see whether you
could implement (or integrate) a container within ZOE to allow you to run
IMAP.
Well... this is what I would like to avoid in the first place.
Thanks for the walkthrough in any case :) Hopefully I will not need to "highjack" James IMAP implementation to turn it into something it was not mean to be.
That said... I still think there would be some values in repackaging James different protocol stacks to make them more accessible to third parties. Something to think about perhaps.
Cheers,
Z.
-- http://zoe.nu/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
