getting ready for client/server architecture

There are a few things that need doing to get things ready for converting COODBMS over to client/server.

First, I am thinking that none of the existing code will be included on the server side. The DRM has some complicating factors because it needs to run in the server and I believe it is important to keep the client-side as clear as possible, expecially if we are going to have clients written in multiple languages. So I see a need to write client-side DRM classes which are independent of the existing classes.

So if we are starting almost from scratch on the client side, the first thing is to reduce the number of jar files. Common can be folded into CowDb and the existing DRM can be folded into COODBMS. The second thing then is a specialized client-side DRM.

The third item is to address configuration. The current mechanism is fine for CowDB, but simply will not do for a COODBMS server. We need to be able to specify the configuration of various databases without code changes now. So we need to use files. Let's establish a name convention where for a given database file we have the option of having a configuration file. Failing that, we can use a common configuration file. And failing that we can use the default configuration. That should give us enough flexibility while minimizing operational requirements.

None of this should take very long. Then we can start getting serious about client/server.