This has been discussed before regarding to the RPC functionality in JBossCache. In 1.4 and before, we have a "deprecated" RPCTreeCache to address the problem with a RPC layer to share the same channel with TreeCache itself such that a user can make a cache call along with her own RPC calls. I can agree that JBossCache should detach itself from RPC functionality. However if I need to do JBC call along with RPC call, what can I do? I need two things: 1. A wrapper class similar RpcTreeCache for user to register the handler and also the callRemoteMethods. This should be fairly easy already by copying the RpcTreeCache that Brian did. So let's call this class RpcProvider. However, where does this class belong? We know HA-JNDI needs it in clustering. PojoCache will need it. And also some other users like this post: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=93270 So a logical conclusion is that it should sit in JBC library maybe a package name like: org.jboss.cache.rpc.RpcProvider. 2. A way to create and obtain Jgroups multiplexer channel. This is pretty much provided inside JBossAS. However, for standalone mode, what's the best approach? Someone needs to create the jgroups channel and bind it into JMX. Then both JBC (already doing it) and RPCProvider will need to see if it needs to obtain a multiplexer channel. If RpcProvider is detached from JBC, then it will needs it own configuration xml to provide multiplexer service name. An extra file to deal with. So still not ideal. To me, if JBC can directly expose its channel to RpcProvider, then case solved. What do people think? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982598#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...