olger Engels wrote: > > I'm glad to see, that jboss will support pluggable interceptors on the > client side, now. You can do cool things with that. Think of: > > ...
> > o caching interceptor (for getters) How will that work in practice? Aren't the interceptors stateless, without being specific to a particular EJB/component instance? > o invocation bundeling (send an array of method invocations and return an > array of results .. all that in one user transaction) I don't quite get that either - interceptors are meant to be transparent to the client code. So how could a client make multiple (sequential) invocations and have them bundled into a single request? > ... > > o mobility !!! if the caller is a sessionbean, serialize it, move it to > a container on the target, do local calls, return to the originating > container Eeek! > ... > o encryption / signing > If the proxies and interceptor stack are dynamically downloaded, how is the security of the downloaded classes assured? Can the classes be loaded over SSL? Or can they be signed so the client can verify their origin? Luke. -- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.mkeym.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
