"timfox" wrote : One of the selling points of remoting was that we could use the remoting API in a consistent way irrespective of the transport which was plugged in. | | This clearly appears not to be the case with the HTTP transport. As far as I can see, "push callbacks" are currently being done with the socket transport, but they're not Remoting "push callbacks". If I remember correctly, somewhere on the server side there is an explicit call to org.jboss.remoting.Client.invoker(). There shouldn't be any distinction in the way the socket and http transports handle this behavior. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973396#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...