You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Sascha Kulawik <sa...@kulawik.de> on 2002/10/08 21:54:02 UTC

RE: imap in JAMES

Hai Nathan !

I'm still interested in the furthe development of James-IMAP. Currently
I've a lot to do in my all-day-work - so I have no time for the
development of james until November. 
It would be really great, if we could work together on James-IMAP. The
current Version in CVS is the newest - so you can start off :)
If you have any questions, ask me. I know the code :)
I think, at the end of the Month I can help you - then I also want to do
more for James. (But currently I'm coding about 14h/day for my job, so
there is really NO time for doing anything for James.)
If youve readed something in the Mailinglist, you also can see, that I
have a lot of todos for IMAP. It would be great, if you can first find
all remaining Bugs with Mozilla and Outlook.
After that I'd like to see the persistent storage inside a JDBC Source -
but first of all it would be needed, to change the serialisation. 
My Idea is to use JDOM for "serialization" of the Data-Objects and store
them as XML Files, after that it is an easy step for storing them in a
Database in a structured form.
Also there are some bugs, that if your Mailbox "hangsup", you cant
restore the remaining Mails, bbecause they are all serialized Objects.
If you have XML Files for that, it would also be an easy step to find
the errors and change them inside the XML File, without loosing your
mails.
It would also needed to move the CommandFetch and CommandStore in the
package, where all Commands resists. This is remaining from the history.

Greetings,

Sascha


> -----Original Message-----
> From: Nathan Carter [mailto:nathancarter@gmx.net] 
> Sent: Tuesday, October 08, 2002 7:35 PM
> To: sascha@kulawik.de
> Subject: imap in JAMES
> 
> 
> Sascha,
> 
> I noticed that since Peter sent the message below to the group almost 
> two weeks ago, there has not been any IMAP activity.  I was able to 
> build the imap sources using "build -buildfile 
> proposals/imap/build.xml" 
> as Peter mentioned, but on startup Phoenix encounters a number of 
> problems in the configuration files and exits - I have found and 
> corrected one issue, but it seems that there are more.
> 
> Are you able to continue working on the IMAP implementation, 
> or are you 
> too busy at work to continue?   I have quite a bit of time on 
> my hands 
> for the foreseeable future, and I'd like to pick up the effort if you 
> are not able to.
> 
> Nathan Carter
> 
> Sascha,
> 
> 
> >> what is missing for getting IMAP in the Main Trunk
> >> by default as disabled
> >> (and maked unstable) ?
> >  
> >
> 
> IMHO the following issues need to be addressed before
> we can vote the IMAP code into the main branch:
> 
> i) Conclusive summary of what does and does not work
> that can be posted on the web site.  This will enable
> the user community to evaluate it for their needs and
> the developer community to determine what needs
> addressing
> 
> ii) Proper documentation of the code in line with code 
> submission guidelines (basically, Javadoc everything).  This 
> is noticeably lacking.  Hence the code is currenty in 
> violation of Jakarta code guidelines. 
> Personally, I'm a stickler for this one.
> 
> iii) Merge with the 2.1 code base.  Once 2.1 is code
> frozen, relevant changes (changes to James.java,
> service structure related to Andrei's changes) wil
> need to be merged in.
> 
> iv) Release of 2.1 - basically the IMAP code hasn't
> received the attention required over the course of 
> August/September to be included in the 2.1 release (which I'm 
> proposing for October)
> 
> --Peter
> 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
> 
> --
> To unsubscribe, e-mail:   
> <mailto:james-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <ma...@jakarta.apache.org>
> 
> 
> 
> 
> 
> 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>