Hi, I think there is no ready-made here to increase the Ping duration. But one can do (for now) stop the pinger by doing something like:
HostContext.getInvocationHandler().close() . Checkout the impl'n: *.altrmi.client.AbstractClientInvocationHandler.close() method ... Maybe as you mentioned rightly , This should be implemented at each ConcreteInvocationHandler level too so that they can also close/release the socket connections to the server. V i n a y. --- [EMAIL PROTECTED] wrote: > Hi, > > I am trying to use AltRMI in a client server > application. > > I have an example client/server setup working. > > Currently, the client creates an AltrmiHostContext > and > AltrmiFactory. The client can lookup and use a > published object. > > However, the connection to the server is kept up > by the > DefaultConnectionPinger. > > What is the expected life cycle for a [socket] > connection to the > server? > > How does the client indicate that there are no > more requests for a > long time [ie: waiting for the user's next command]? > > Socket management on the server side will be > important for servicing > more clients than available sockets. > > Thanks for the help. > > > Alvin. > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Yahoo! Sports - sign up for Fantasy Baseball http://sports.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
