Fix compile problems on j2se 1.5 - our Queue class conflicted with one in
java.util. Also fix an API issue when running the server on Windows - the
println method sends '\r\n' on Windows instead of '\n' on Unix, which
confuses applications such as ihost.

Patch provided by: skel

Addition to the protocol which completely breaks backwards compatibility.
Seeing as we sent the FQDN, we may as well tell them the IP too. It seems
oddly hard to reliably work these out on the host itself.

More explict checking of the last modified value.

Fairly major commit. This will break the current version of ihost, but this
had to be done really to give Pete something to test the new ihost against.

The main change here is removal of the TCP Heartbeat functionality from the
filter. This meant the following features stopped working :-
  - Heartbeat testing
  - Configuration checking
  - Service checks

The heartbeat testing, specifically the monitor, now looks at the presence
of UDP packets instead. Before it just looked for the presence of a TCP
heartbeat packet, so the change their is fairly negligible. Of course this
means heartbeat testing now relies on the UDP working... but I don't see
this as a problem.

Configuration checking has been repositioned in to the filtermanager. This
is a backwards compatible change - the filtermanager should still perform
as it should for older hosts. But now there's an extra command to check the
configuration is up-to-date, with a similar format to the old TCP protocol
in the filter. (although we may optimise this soon)

The service checks are broken. This isn't a major issue for us as they were
pretty useless in the first place. The concept is good, but the checks are
just far too primitive. I expect at some point I'll work on a seperate
component that just monitors services, which will replace this function.

Further changes in the server include removal of the key checking code,
as this relied on a bolt on to the TCP heartbeat protocol to ship the
key. This got more akward than originally planned, so I'm happy to drop the
idea. In the long term we hope to replace this with a public key systems
for signing and even encryption.

Finally, general tidy up to remove other bits of code that check for
TCP heartbeat packets when they don't need to any more.

Fix for upgrade to Jacorb 1.4.1. It's our fault actually, we've not been
correctly using the names when binding to the Naming Service. This needs to
be fixed properly at some point, but for now I've changed changed the code
so it "means" the same as it did before the upgrade.

A fix for a COMM_FAILURE that keeps getting out. I think this is happening
when the FilterManager tries to query the filter. It shouldn't really
happen, but it seems it does. It begs the question as to whether every
CORBA communication should be wrapped in one of these... which would
unfortunately include every logging line :/

Split the CORBA side of the filter in two. The Filter interface still does
the receiving of data, just like it used to. This can optionally be turned
off in the configuration if required. The new interface, FilterInfo, is
used to provide information (host and ports) to other parts of the server
about the Filter - namely the FilterManager. This split has been done so
that the data receiving part of the Filter can be turned off, without
breaking the FilterManager.

The whole server package structure has been changed.
Old Package: uk.ac.ukc.iscream.*
New Package: uk.org.iscream.*

Given all the classes that extend Thread a name using Thread.setName(). It is
only representative as far as it will tell us which class the Thread is, but
this will go some way to aiding debugging. If time permitted, more effort could
be taken to name each thread according to what it was dealing with.

Now catches a more specific exception to the problem. Note that the
ReferenceManager catches the CORBA exception, and throws it's own, so
we need to catch that instead.

We'll send FQDN's in lower case... just to be consistent.

That was such a dumb mistake. I should learn not to copy and paste from other
code :)

Better error printing.

Some tidying up.

fixed typo

Had a tidy up. The Filter Manager now makes use of the Reference Manager, which
ensures that we don't have lots of messy reference passing.

Made changes to fit into the new package structure.

Added the required extra functionality that the was required to complete the
setup with the host.

Added features to support the verbosity levels now provided by the logging system.

Stupid mistake. :-(

Initial check in of the FilterManager

Current support for Host connections and passing back configuration.

Support missing for filter contacting etc.

Not finished or fully commented.