I agree w/ this, although I think it's a shame not to make JBC somewhat more extensible in this area. Extensible in the sense of being able to add new types of JBCMethodCall. (Maybe people can; my impression from a couple months back is you can't.) Extensible for the purpose of adding new/improved caching behavior, e.g. acquire a lock around the cluster or something. May be a bad example. But if people can add a new JBCMethodCall, they can add new functionality, which may get contributed back to the core project. Right now this is very difficult to do. Solving this kind of problem is not trivial either, since the interceptor behavior is tightly bound to the type of method call. But it's something to think about -- someday when we all have free time.... For generic RPC functionality, unrelated to core caching functions, I think the way to go is to use two channels with a multiplexer. jboss-dev-forums-bounces(a)lists.jboss.org wrote: Brian Stansberry Lead, AS Clustering JBoss, a division of Red Hat Ph: 510-396-3864 skype: bstansberry