Norman Maurer wrote:
Hi guys,
as you (hopefully) all know the current Quota code is very ineffectiv
and can cause many problems when using JDBC based mailrepository.
See:
http://issues.apache.org/jira/browse/JAMES-717
http://issues.apache.org/jira/browse/JAMES-718
For me there are 2 possible solutions at the moment for getting rid of it:
1. Add an comment to config.xml to explain the problems with this
matchers and mark the matchers as experimental.
+1
2. Remove the code until we can provide a "usefull" support for quota.
For me thats impossible until we add the quota support to the storage
layer (Mailbox). This will propally not be done until we break storage
comptatibility
+ 1
+0 for a backward compatible release
+1 for a backward incompatible release
A further option would be to add a "fullsize" property to the
MailRepository interface, load full size once at first load (or the
first getFullSize call) and then intercept every store/remove to
dynamically change the "cached" fullsize.
This would return inconsistencies if the repository is altered on the
storage level (without using the MailRepository interface) but this
would probably be much more performant.
Not sure if anyone want to work on a similar issue, and if it worth
working on this as we'll probably deprecate the MailRepository in the
next backward incompatible release.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
