Tidy up of the client interface code - more commonly known as the
"right hand side of the server". Right since the start the filter
side of the server has been nice and tree like - every Filter sent
data to another Filter. At the top of the tree there was a "special"
Filter known as the RootFilter, which to the other Filters just
looked like a normal Filter. This was nice, and simple, and expandable.

The Client Interface on the other hand was messy. The root filter
had some hacky wrapper threads which pulled from a queue and pushed
to the relevant client interfaces (one for real time stuff, and the
other for databases). There was no simple room for expandability -
it was all hardwired to do just what was needed at the time.

This commit changes that. A Client Interface now connects to another
Client Interface, with a special one being found in the RootFilter
(yes, maybe that needs a name change now :-). So we can chain client
interfaces, and move other bits and bobs around in the server - for
example, alerting no longer needs to be connected to the Client
Interface, it can connect straight to the RootFilter (or, wherever
the config tells it ;).

Hopefully this sanitizes the underlying layout of the server a bit.

As a final note, I dropped the DBInterface. This used to insert
data in to a MySQL database. We've long since stopped using that,
and it's fallen behind and is way out of date. For now, it's gone
in to the attic.

Added URL to GPL headers.

FilterManager's can now have their own individual configurations. I want to
run more than one, and I want them to have different setups. Specifying a
name for a FilterManager is similar to that of a Filter. There is a "-fm"
flag to the startup which allows you to set it. It will then request a
configuration of "FilterManager.<name>".

Changed a funny character (c) to a plain text (c).

Slightly more accurate output.

New dependency checking. The old method was to attempt to start a Component, and
if it failed, it probably had a depdency problem. The approach now is to ask the
Component to perform a dependency check first, then if this suceeds, have a go
at actually starting it up.
The actual dependency check is a bit neater and more precise than before, and
should be much more fool proof. The order the components are specified in the
default.properties file is now irrelevant, although the "correct" order would
certainly increase booting time.

Now detects loss of CORBA comms and restarts...hopefully ;)

better config handling for the timeout

bug fixes

debug code added

bug fix

bug fix

fixed concurrent modification exception

bug fixes

bug fixes

initial support for CORBA retries

Been meaning to tidy this bit for some time. Now handles the command line
arguments better, and supports them all :-)

Changes to reflect move of Component, ComponentStartException, and the
ReferenceManager from util to componentmanager.

no supports Filter component

now supports dbinterface component

now supports FilterManager

initial checkin

This componentmanager will be the way of starting the system
Currently only the core component is supported