I beleive we need to go through our Coding Standards document,
purge some items (since they do not apply to modern JVMs) and
incorporate ideas from this list of documents:
Twelve rules for developing more secure Java code
-------------------------------------------------
http://www.javaworld.com/javaworld/jw-12-1998/jw-12-securityrules_p.html
Design for performance, Parts 1 - 3
-----------------------------------
http://www.javaworld.com/javaworld/jw-01-2001/jw-0112-performance_p.html
http://www.javaworld.com/javaworld/jw-02-2001/jw-0223-performance_p.html
http://www.javaworld.com/javaworld/jw-03-2001/jw-0323-performance_p.html
Before we get into another debate for the bracketing of the code, I am not
addressing that. I am addressing the fact that we want our code to be:
1) Secure--we are targeting servers
2) Scalable
3) Developer Friendly
4) Fast/Performant--servers shouldn't waste milliseconds
This is the priority of goals--and I think we should incorporate that much
on our site.
What I want us to do is to reduce the redundancy of statements in our
coding standards, incorporate the 12 points of security rules, and if
possible add something for the performance design. We want to let the
docs state our priorities.
<remember>
This is not a discussion of formatting styles. This is a
discussion of identified and quantified areas where these
programming idioms provide real benefit. In short, the
discussion should only about technical programming idioms
not preferencial style.
</remember>
S/MIME Cryptographic Signature
