Updating subject while service is deployed

I'm thinking about the ability to update the Subject a service operates
under while it is active. The use case is that during the life-time of a
service it is very well possible you want to add an additional identify
a server can authenticate itself as. While this is not something I want
to implement as of today I would like to make choices now that would
ease the implementation at a later date.

However this raises an issue as the semantics for
BasicJeriExporter.export() state that during dispatching the security
context is restored as was active when export() was invoked. When the
subject 'changes' I can always 'activate' another subject by overriding
InvocationDispatcher.dispatch() and perform a Subject.doAs() with the
new subject and then calling the dispatch() method at the super class,
although I have no idea what the consequences might be of this. Or in
other words are there parts in the current implementation that relies on
the subject never changing, I think of caching, etc.

Any help to shed some light on this issue would be appreciated.
--
Mark

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]