Hi guys, In my client implementation, the user starts the client by typing out the host name and port number in the command line arguments. Now suppose after connecting with the server, there was a connection failure. So the reference to remote object now is invalid and cannot be used to interogate the database on server. So should i provide an option in my client's menu system to reconnect with the server? In my present implementation the user has to restart the client to reconnect with the server. Any suggetions...
So should i provide an option in my client's menu system to reconnect with the server? In my present implementation the user has to restart the client to reconnect with the server.
I did exactly the same as you. If there were a failure after client initialization, then a restart was necessary. It would be a nice feature to be able to restart the client, but I don't think it is a necessity. Hope this helps, Michael Morris
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher
I agree with Michael that a restart is probably just fine with the assessors. However, since my code was already encapsulated into an object that could take a String (hostname) or a File, and create the necessary connections, adding menu items to open a local file or connect (or re-connect) to a server was trivial, so I did it. I would say as long as you don't have duplicated code, you should be OK.
Joined: May 02, 2002
Hi guys, I have not provided the reconnect feature on the client. Although i can easily reconnect by passing string parameters to the ConnectionFactory but i feel that this part is unnecessary. Any suggetions...