Re: [IMAP] Design flaws / Performance problems

2010-06-17 Thread Norman Maurer
Hi Eric, yes this is true for all folders not just for INBOX (this was just and example). About the size field I think that make sense. This would allow to add quota support on top easily. For my second point I made a mistake. its not the first recent message. Its the first unseen message. Our im

Re: [IMAP] Design flaws / Performance problems

2010-06-17 Thread Eric Charles
Hi Norman, I suppose it is applicable to all folders (Sent, Trash,...) and subfolders of INBOX (for example) ? Could we also have the same logic for the size field ? About your second point (the first recent message), I don't find my way. Why is it needed by imap and where is it implemented ?

Re: [IMAP] Cut a milestone ?

2010-06-17 Thread Eric Charles
Hi Tim, Sorry, "message_id" was indeed needed in the patch, otherwise you've got a id column which is pk and fk. I still made some additional tests, and omitting the @JoinColumn also works. DB is created and mail delivery is correctly working when you apply on JPAProperty. As soon as you appl

[IMAP] Design flaws / Performance problems

2010-06-17 Thread Norman Maurer
Hi all, after testing a bit around with current version of imap I noticed some design flaws. These flaws just kick in when you have a lot of mail and slow things down.. So here is what I found and how I would like to fix it: 1) When selecting a Mailbox (a select INBOX) the count of all messages a

svn commit: r955582 - /james/jdkim/trunk/main/pom.xml

2010-06-17 Thread bago
Author: bago Date: Thu Jun 17 13:11:38 2010 New Revision: 955582 URL: http://svn.apache.org/viewvc?rev=955582&view=rev Log: Cleanup plugin versions and rat configuration. Modified: james/jdkim/trunk/main/pom.xml Modified: james/jdkim/trunk/main/pom.xml URL: http://svn.apache.org/viewvc/jame

Re: [IMAP] Cut a milestone ?

2010-06-17 Thread Eric Charles
Hi Tim, Comments inside. Tks, Eric On 06/17/2010 12:58 AM, Tim-Christian Mundt wrote: Hey Eric, For example, with Derby, the schema is create with GENERATED ALWAYS columns and not GENERATED BY DEFAULT. Why's that? Wouldn't GENERATED BY DEFAULT solve this problem so we could happily

svn commit: r955534 - in /james/server/trunk: core-library/pom.xml dnsserver/pom.xml

2010-06-17 Thread norman
Author: norman Date: Thu Jun 17 10:06:42 2010 New Revision: 955534 URL: http://svn.apache.org/viewvc?rev=955534&view=rev Log: import postbeanprocessors in dnsserver osgi bundle osgify core-library (JAMES-835) Modified: james/server/trunk/core-library/pom.xml james/server/trunk/dnsserver/p