This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
My remote server is now just a command line program. Do you think it would be nice to have some kind of server window which tells that server is running? It would be nicer to close the server window than to type Control-C. Jukka
It would certainly be nicer. But is not mandatory, and in fact a lot of people here just kept the command-line version of a server. So, it really depends whether you feel confortable enough that you will develop a server GUI that makes it more user-friendly ... Hope this helps Stephane
I left my server command line only just because that is the industry standard for most of the server software I've come across. Remember that this will run as a background daemon, and if you write it well, the administrator will rarely if ever think about it. I'm sure either way is fine, but having to have a window visible (which can atually cause problems on headless servers) in order to run the server seems very odd. If anything, the slickest thing to do would be to have your server GUI communicate with a separate process so you could start the server, monitor it's state, but then close the GUI and leave the server running, and then later start up the GUI and shut down the server.
i've provided a simply jframe with a 'block database' button (to check that issue), a 'close' button and a jlabel with the number of active connections. all in a simply class (no mvc separation at all) as the efforce for it was minimun