Originally posted by Klaas van Gelder:
No, I only use locking in network mode, because the locking mechanism is only required when the database is concurrently accessed by different clients ! The locking mechanism is completely bypassed in local mode.
Therefore, I implemented locking in the remote class (FlightDataImpl) which of course belong to the network module.
Originally posted by Andrew Monkhouse:
Like No�l, I dont like the idea of a package with a single class - I don't think it adds to the comprehensibility.
I started by looking at your package names, and based on them (ignoring the class names themselves) trying to work out which package I would look in for the class to start up the client / start up the server. Unfortunately this was not obvious to me. My first choice (nl.kvg.flybynight.gui) only has an Exception class. Then I don't know whether to go for your controller package or your swing package. Note: This is a bit of a personal observation - different programmers look at code in different ways, so someone else could find the classes very quickly and easily.
I did consider using my own domain name as a package name, but decided that there was little value in it - since Sun had already given us the suncertify.db package, I decided to follow suit. For what it's worth, here are the package names I ended up with: