I always found the storing of the key inside of the cipher object to
feel strange. I guess Cipher's just "feel" stateless to me. So -
having two interfaces for this feels like it'd be more confusing to a
new user and over-engineering.
If anything, seems like the default implementation should be stateless
with a subclass that is stateful - not the reverse. It feels more
natural to have a Cipher interface with a subinterface called
StatefulCipher or KeyStoringCipher rather than the other way around.
Just my opinion...
On Dec 11, 2008, at 11:57 AM, Les Hazlewood wrote:
I just created this issue: https://issues.apache.org/jira/browse/JSEC-36
Any objections? Thoughts?
