Bernd Fondermann wrote:
Hi,
I uploaded the current code into JIRA JAMES-442
(http://issues.apache.org/jira/browse/JAMES-442)
I looked around in the code when you uploaded them: I saw you left the
old source folder, too (that should be removed, it is confusing).
There is much more which comes to my mind as possible future developments:
+ codebase: where should the whole application be placed (own
subproject, sandbox?)
I think in its own subproject.
+ libraries: Remove dependency on Ristretto
+1
+ architecture: integrate with maven2
+1: jSPF is maven2, I would like to have a common way for all
subprojects. (Maybe we can convert Mime4J and Jsieve, also, in future)
+ feature: add option to make the load adaptive, so that we can get
to the limits of James
+1 My preferred feature ;-) I would like to use it to test optimizations
and be sure we don't introduce bottlenecks with changes.
+ feature: do more functional testing, not just pure end-to-end
tests, by parsing the received mail and check if, for example, a footer
had been added.
Maybe this is much more a functional test that could be added to the
default unit tests.
+ infra: use it as an Continuous Integration tool which
automatically executes on Daily Builds
That would also be cool.
+ reporting: draw fancy graphs
Not important at all, even if people like fancy graphs.
+ integration: look into JMeter integration
Yes, maybe this could help creating custom scenario, and maybe the best
feature would be an SMTP proxy to log an SMTP session and add it as a
template of the load test (JMeter do that for the HTTP tests).
+ development: have a review of the whole stuff, take it apart, improve
it and put it together again ;-)
I'll be heppy to help in this!
What do you think?
Bernd
Thank you again for your efforts in creating tests and load tools to
increase James reliability!
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
