Originally posted by Jan Groth: i agree with you. i wrote 4 windows, overall:
- a server gui to specify data file and start / stop server - a filechooser for standalone mode - a ip-chooser for client mode - the main gui, of course
hope it helps, jan
I was gonna just provide a stop button. My start server was going to be done programmatically when starting in server mode. Why provide a start button as well ?
I have also seen metion of being able to provide a Server Port. Any reason for this cause I wasn't going to ?
Joined: Feb 03, 2004
in principle, you are right...
providing start / stop facilities makes debugging a little easier, and it's not a big deal in terms of extra code. just an unbind() method more.
if you take setting the server port for example, it is a bit more tricky. first of all, i don't see any benefits, actually i never had anything running on 1099 but rmi, so i really think this does not have to be configurable by any big technical needs. second - it's another set of problems you might have to deal with - what are valid ports, what is if someone configues it to port 80, ... ?
so, to come to my point - i'm trying to find a balance between required minimum and comfort. that's it...
many greetings, jan
ps: in my assignment, a "unbook / release" functionality wouldn't be required, and andrew mentioned people passing without this functions. wow, that would be too hard-core for me... :-)