Hi Robert,
Regarding caching the connections on the clients, do you know if there
is an overhead in the server for each client that creates the object
on the server? What I mean is, lets say that I will create the object
on the client, keep it alive and use it whenever I need. Does the
server allocates some memory or any other resources for each object
created?
Thanks
Robert Klemme - 23 Apr 2007 14:27 GMT
> Regarding caching the connections on the clients, do you know if there
> is an overhead in the server for each client that creates the object
> on the server? What I mean is, lets say that I will create the object
> on the client, keep it alive and use it whenever I need. Does the
> server allocates some memory or any other resources for each object
> created?
I guess the server will somehow count number of client objects (or hold
a reference per connection), in order to make sure the server object is
not collected before all client stubs are.
robert
Esmond Pitt - 24 Apr 2007 08:14 GMT
> Regarding caching the connections on the clients
RMI does TCP connection pooling. The client reuses idle TCP connections
that are up to 15 seconds old. Idle connections older than that are closed.
> do you know if there
> is an overhead in the server for each client that creates the object
> on the server? What I mean is, lets say that I will create the object
> on the client, keep it alive and use it whenever I need. Does the
> server allocates some memory or any other resources for each object
> created?
I don't know exactly what 'object[s] created' you're talking about here.
A thread is allocated at the server for each open TCP connection, which
exits when the connection is closed as per above, or after a maximum of
2 hours. All that is tunable.