Noel J. Bergman wrote:
That requires a bit of thought, rather than rushing into coding
I'm against this fear of coding.
Writing code many times takes much less that discussing and it decreases
the misunderstandings because we all share the JVM/Java specification
knowledge.
I have lost the count of discussions with no end, with no conclusions,
or even discusssions with conclusions but with no one that ever
implemented them, or discussions with conclusions but that as soon as
you try to implement them you discover that you forgot to take a
specific issue into consideration.
I'm sure I can find discussions about virtual users at least 3 years old
in the James archives: I browse/search James archives at least 15
minutes per day (TO be added to the hours spent on the daily messages).
Btw I think the most important steps have been done:
http://issues.apache.org/jira/browse/JAMES-426
http://issues.apache.org/jira/browse/JAMES-508
Now we have the basis to introduce the feature.
If you search the archives I proposed this roadmap almost an year ago
but the discussion was never finished.
I prefer to receive vetoes or to revert something I already committed
than discussing full days and resulting in nothing done. At least in the
first case I have new code I like in my local james and if I am lucky
enough you like it too and when we finish the discussion "post code" we
already have the feature.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
