Am Freitag, den 19.05.2006, 12:40 +0200 schrieb Joachim Draeger: > Hi Stefano, > > Stefano Bagnara wrote: > > > I will try to submit soon an updated imap2 proposal (updated to build > > against the current trunk), so you'll have an updated source to start > > your work from! > > I have already made some efforts in that direction. The main problem for > me was the in memory store because I need something to "touch" when > working with code. I guess many people feel the same and that's a reason > why there is so less success with it. > So I began to fix it to let it compile against trunk and added a, guess > what, Javamail backend. For traceability I tried to touch as few of the > existing code as possible. I wanted to clean my code a bit before > publishing it. But if people are eager I could put out what I have in > the next week, okay?
Sure upload your work to jira. We intressted in such work .. Maybe we can help clear up things after read the sourcecode.. > > At the moment my backend is not very stable and it is only supporting a > few operations. > The existing frontend part of the Imap2 proposal looks quite > sophisticated even it is not easy to understand. But I think that is due > to the fact that Imap is a *very* complex protocol. Pop3 is breeze > against that. > I have seen a compatibility chart for the existing code that looks quite > impressive. > > I suggest the following steps: > > 1. Implementing a backend for the existing code. For me that is > unavoidable before further steps. Javamail has everything that is needed > for that and it shouldn't be too much work. Before starting a big > discussion: I'm just talking about a wrapper for the existing > interfaces. No serious design decision for Javamail is made at this point. > > 2. Documentation for the existing code. Maybe some fancy UML, or just > prose. Just how it works and how components are interacting. I think it > is important to understand the existing code before making too much > changes to it. > > 3. Discussing the existing architecture and talk about an adequate backend. > > Joachim Bye Norman
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
