anonymous wrote : | What I don't agree with is the need to have callback servers, as in pieces of code wrapped around server sockets on the client side . Once you have a TCP/IP connection from client to server, use that and don't open another one from server to client. | Although a callback server is needed on the client side, this does not necessarily mean a server socket is needed. If using the multiplex transport, it can use the same client socket to receive call back from the server (using virtual sockets). I have tested this through my firewall and know that the multiplex transport supports this. So think the functional requirement of multiplex is already met. Now would be a question of either performance not being good enough or programming model not fitting. I agree that we need Ron's input as to how much more performance gains can realistically be expected of the multiplex transport. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979236#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...