Though this isn't set in stone just yet, I'd like to have a better integration between transaction managers/resources and Remoting. Getting transaction timeouts to sync up is definitely part of this. But another key point with Remoting 3 is that the client-connection relationship is changed as well; you generally won't have a timeout associated with a connection anymore. The responsibility to time out a single request will be with the user code.
See these methods for more info on that: http://docs.jboss.org/remoting/3.0.0.GA/api/org/jboss/remoting/Client.html#send(I) whose return value has this method: http://docs.jboss.org/xnio/1.2.0.GA/api/org/jboss/xnio/IoFuture.html#await(long,%20java.util.concurrent.TimeUnit) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216405#4216405 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216405 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
