Currently we have: * derby.jar (embedded, engine) * derbynet.jar (network server) * derbyclient.jar (network client)
I would like to add derbyserver.jar which includes everything from all of these to form a complete standalone server; the client is included so that people don't need to switch classpath if they want to use a remote server and so that stored procedures can access remote servers.
If we do this was can also potentially drop derbynet.jar as it is not usable without derby.jar.
Any objections? -- Jeremy
