How many client and server sockets does the current RMI implementation use?
posted 9 years ago
Can someone confirm whether the following statements are true:
1. each client "lookup" of a remote objects results in a unique client side socket.
2. each remote object type will be exported to (typically anonymous) unique port.
3. So the number of sockets used on both the server and client side equates to the number of remote objects (assuming a client normally perform one lookup for each remote object once.)
And here's a related question:
1. Does existing RMI multiplexes a socket with a number of remote objects (each being different type)? If not, is there a way? Do we do that through custom socket factory and custom socket, where perhaps the added logic of multiplexing happens? Is this a good idea to improve performance?