Hi!
There is this one change of the database layout which should be decided
upon before releasing, I think. Messing with code after the release is
fine, but changing the database would be bad. I'm talking about Normans
idea to unite the Message and Membership interfaces/classes => tables.
The original idea of separating those was not to pass the whole mime
message around when just the flags are needed. Moreover, the Membership
part would serve as a reference to the Message so that a copy would just
mean another reference to the same mail.
The question: does the increased complexity really pay off? I think
saving space is not really an argument because it's not really common to
have duplicates (at least in my experience). And loading the "whole
message" would not mean the contents but only a stream handler, not a
memory killer, right?
Regards
Tim
Eric Charles:
Running here without any problem jpa (embedded derby) + jdbc
domainlist + spamassassin + forwarding mailet.
When do you think to release?
Tks,
Eric
On 06/07/2010 04:51 PM, Norman Maurer wrote:
Thx mate..
I deployed fresh trunk and everything seems to work so far without
problems :)
Bye,
Norman
Ps: I'm using JCR Mailbox
2010/6/7 Eric Charles<eric.char...@u-mangate.com>:
Hi,
I will deploy a fresh trunk this night just to make sure everything
is still
ok (cfr last commits in protocol,..).
The last snapshot I took is 2 weeks-old and is really stable.
Tks,
Eric
On 06/07/2010 04:40 PM, Norman Maurer wrote:
Hi all,
I think all the stuff in the imap library is now very usable. I think
we should cut a milestone and then cut one of james server. Anything
you guys want to get refactored before ?
Bye,
Norman
Ps: Even if we discover a bug later we can cut just another one..
Release often, Release early (urgh...)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
