server shutdown

[Aruna Raghavan]

Hi,
I am trying to wrap up the project and come up with all sorts of last minute questions...
I have small screen for server configuration. It dispapears as soon as the server is started up successfully. Is there a need to add shutdown option to it and keep it visible?
Thanks,
Aruna.

[John Smith]

I have small screen for server configuration. It dispapears as soon as the server is started up successfully. Is there a need to add shutdown option to it and keep it visible?

The extra features can only lower your score, and I am puzzled as to why people insist on coding these extras. I had no server GUI, no graceful shutdown, no Unreferenced, no timing out of connections, no cleaning of stale clients, no dynamic downloading of stubs, no codebase or classpath parameters, no policy files or security managers, no unlock(-1), no server re-connect, no integrated server help, no ability to manage your stock portfolio, no flashes or pretty flowers of any kind, and I got full score for my server design. If this is not convincing, consider this: none of the features listed above are in the requirements and they add absolutely nothing to simplicity, clarity and reusability of your design.
Eugene.
[ January 22, 2003: Message edited by: Eugene Kononov ]

[Aruna Raghavan]

Thanks Eugene,
Just what I needed to hear . I did the server GUI because on both server and client sides, it allowed me to add online help. Some how, writing an ascii user manual that just sits in one dir did not appeal to me. I promise not to add any more bells and whistles.
Aruna.

[Aruna Raghavan]

Oh yes, and then there is the possibility of admin typing the wrong java options. I wanted to have little possibility for that. With the small gui screens I did, he can still enter bad data but atleast he won't type -D options wrong...