No to anycasting and oob. No feature without a clearly defined use case, particularly not at this stage of the game. :-) It needs to be an overloaded method. Last but not least, we can't leak the RspFilter interface through the HAPartition API. HAPartition is meant to be an abstraction that hides the use of JGroups. Originally, when JGroups and AS clustering was new, hiding it to allow using something else underneath. That's unlikely to happen but I don't want to break the abstraction. More directly relevant, the ha-server-api project has no dependency on JGroups, and thus consumers of it don't either. I want to keep it that way. I think what we need is an org.jboss.ha.framework.interfaces.ResponseFilter interface (spelled out, not RspFilter) in ha-server-api. Then in the AS cluster module org.jboss.ha.framework.server an adapter class that implements RspFilter and delegates to a constructor-injected ResponseFilter. ResponseFilter can't expose Address either; should be ClusterNode. The adapter class needs to do the translation. :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163166#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...