On 11/26/08, Patrick Ruhkopf <[EMAIL PROTECTED]> wrote: > Thanks for the prompt response, Robert! Glad to hear that you are > enthusiastic about the idea like me.
:-) > On Tue, Nov 25, 2008 at 3:19 AM, Robert Burrell Donkin > <[EMAIL PROTECTED]> wrote: >> But if you're interested in helping out with IMAP development then we >> can take a branch and start working. > > Sounds like a plan. Frankly I don't know much about the imap > protocol. You're timing's good :-) It took me about a year to learn enough about IMAP to create a working implementation but the good news is that the hard leg work's over now - a comprehensive functional test suite exists together with working IMAP commands and codecs. The torque implementation sucks but I run around 1G of mail on it ATM and it's usable. > So if "revising data access" means interface changes I could probably > only make suggestions from the JCR point of view and not much of the > other side of the interface. You know what I mean? If on the other > hand it's only about replacing the legacy implementation then I guess > the task would be easier for me to tackle. The torque implementation makes some very poor design choices. The interface between the data access and processor layers is too complex and lacks elegance. > If you think it makes sense let me get a little bit more familiar with > the code base to get some idea of how much effort is involved and how > well the current data access api would play along with JCR. I'd much rather start from first principals by designing a good model. I'm very familiar with the actual requirements (rather than the API's requirements). Second, create a fully working and tested module just containing the JCR stuff. Third, create an adapter module (probably by cloning the torque module) between the API and the JCR module. The good news is that it should be possible to get something that runs (about as slow as Torque) without too much effort since a lot of the complex stuff is implemented programatically. Sound like a plan? Robert > > Patrick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
