Ron, you can use one of the Client.addListener() methods that supports uni-directional callback polling (which will simulate push callbacks by using internal polling for uni-directional transports). Can use the same method when using bi-directional transport (for true push callbacks on same socket connection), so there is no code change needed when switching transports (i.e. from http to multiplex). The javadoc explains which addListener() methods would be best fit (see http://labs.jboss.com/portal/jbossremoting/docs/api/org/jboss/remoting/Cl...). These methods were added in May per request from the messaging team (http://jira.jboss.com/jira/browse/JBREM-363). Can also take a look at org.jboss.test.remoting.callback.push.unidirectional.CallbackPollTestClient to see it in use. For the uni-directional transports, probably the only config that you will want to consider is callbackPollPeriod (org.jboss.remoting.callback.CallbackPoller.CALLBACK_POLL_PERIOD), for setting how often client should poll for callback messages internally. As for type of streams being passed to marshalling layer, I would still be willing to change the remoting code (socket invoker in particular) so that marshalling layer is never passed an object stream but just the raw stream. However, this seems to be the opposite of what asked for in http://jira.jboss.com/jira/browse/JBREM-371. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973466#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...