Sim IJskes - QCG wrote:
Peter Firmstone wrote:
I've also created a new interface RevokeablePermissionCollection,
with the ability to revoke(Permission ... permission) for read write
PermissionCollection's and revokeAll(Permission permission) for read
only and read write PermissionCollection's. My implementation wraps
any existing PermissionCollection, the wrapper is also using a
ReentrantReadWriteLock to allow concurrent reads and synchronized
writes. I figured this would fit in nicely with DynamicPolicy.
Am i right in thinking that this would help to make jini more
'embeddable'?
Gr. Sim
I think so, it's still an early implementation, I don't understand the
full ramifications yet. It should benefit any environment where it is
undesirable to shut down the jvm to remove Permission's.
Regards,
Peter.
