execution arguments

friends,
1. when starting server argument should be mode.(local or remote).
2. when starting client , path of db should be given in local mode and host & port in remote mode.
am I right?

Server does not need to know about local or remote mode. Server only needs to be started when running in remote mode.
The client needs to choose whether it runs in local or remote mode. When running in remote mode, client will need to know the host and port of the server.

yes, I understand.

In my application, server binds Connection object to registry running in Registry.REGISTRY_PORT. so it is sufficient for client to provide host of server.
Am I violating requirement?

I think it's fine as long as the client knows it always uses the default port 1099. I don't think Sun requires the assignment to run on other ports, but I did write my project to run on any valid port.

In that case, Robin, how will u pass port number from client to server? (if client chooses some port..)

You don't pass the port number from client to server.
First the server is started on a particular port number. Then the client needs to select that same port number either through a command line argument or through a GUI. Both the host and port would be included in the client's JNDI lookup of the remote object.

In client/server case, where would you specify the db file name. While starting the server, or the client?
If you specify while starting the server, then only thing you would need to specify on the client is the host and port of the server.
However, if you allow the flexibility to choose the db file name from the client, then the server needs to be capable of handling multiple db files concurrently.
To me, it is not clear from reading the specs, if SUN wants us to do this.
Any one?