configuration parameters

[Charles Dupin]

I was intending to start the server with the parameters:
-Djava.rmi.dgc.leaseValue=2000 -Dsun.rmi.dgc.checkInterval=1000
But the submission req says:

The command lines may only take configuration parameters selected from this list:
DNS name of the server
Port number used by the server
Data file name(s)
java.rmi.server.codebase
security manager policy file

What do you recommand?
C.

[John Smith]

What do you recommand?

I recommend:
java -jar server.jar
java -jar client.jar
Eugene.

[Prakash Krishnamurthy]

Eugene:
By doing so, where have to specified the sever name, port etc....?

[John Smith]

By doing so, where have to specified the sever name, port etc....?

The server program doesn't need to know the server name. As to the client, the user specifies it in the GUI. Regarding the port, 1099 can be assumed if not explicitely specified.
Eugene.

[Charles Dupin]

Eugene
if you dont specify -Djava.rmi.dgc.leaseValue=2000 -Dsun.rmi.dgc.checkInterval=1000
your server does not check for lost connections, isnt it. But may be you have another way to do it. I mean to enable the unreferenced...
Charles.

[John Smith]

if you dont specify -Djava.rmi.dgc.leaseValue=2000 -Dsun.rmi.dgc.checkInterval=1000
your server does not check for lost connections, isnt it. But may be you have another way to do it. I mean to enable the unreferenced...

You don't need to check for lost connections, don't risk losing points.
Eugene.

[Peter den Haan]

Originally posted by Charles Dupin:
if you dont specify -Djava.rmi.dgc.leaseValue=2000 -Dsun.rmi.dgc.checkInterval=1000
your server does not check for lost connections, isnt it.

It does. It just takes a bit longer to discover them. So what.
There is nothing wrong with documenting these flags as an optional way to tune the timeout in your "administrator's documentation". There is no need for the assessor to use these flags. The cleanup is not required and consequently the assessor won't need to use these flags.
- Peter