>> Ok I see. I will start with some simple read and write security impl. >> I think that comes "permission on method and class" relativ near, or? >> For that I will create an own sub-package >..simplestore.persistence.security. Ok? >> This will be the place for java.security.acl implementations. I will start >> implementing this and then we will see how this object stuff fits in. >> >> Maybe PersistenProxy gets an second constructor, or something else to >handle >> this securtiy things or not. >> >> What do you think? >1.Yes permission on method or class is the same for implementation. >2.implementation for java.security.acl.* is good idea
Ok kool. BTW I see no need to implement an extra interface for that. Just implementing the securtiy.acl interfaces is ok, or? Or do you want an extra interfaces in our commons.simplestore.persistence package? ~Gerhard ----------------------------------- Boren's Law: When in doubt, mumble. ----------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
