Revision 1.9 - (view) (annotate) - [select for diffs]
Fri Mar 16 16:11:31 2001 UTC (23 years, 2 months ago) by tdb
Branch: MAIN
CVS Tags: PROJECT_COMPLETION
Changes since 1.8: +30 -3 lines
Diff to previous 1.8

Implemented Queue size limiting.

Added finalizers to the debugging. This could be very useful to know.

Revision 1.7 - (view) (annotate) - [select for diffs]
Fri Mar 16 01:50:36 2001 UTC (23 years, 2 months ago) by tdb
Branch: MAIN
Changes since 1.6: +12 -3 lines
Diff to previous 1.6

When a CORBA Client disconnects it is caught in the DataHandler. But this would
leave the ControlHandler just lurking about, so we now explicitly make an effort
to close it down, and disconnect it from the ORB.

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

Revision 1.5 - (view) (annotate) - [select for diffs]
Tue Mar 13 02:19:44 2001 UTC (23 years, 2 months ago) by tdb
Branch: MAIN
Changes since 1.4: +5 -2 lines
Diff to previous 1.4

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.

We need to shutdown the Monitor's when closing down, otherwise the Queue's never
get destroyed... and just sit there idle'ing away :)

Revision 1.3 - (view) (annotate) - [select for diffs]
Mon Feb 5 03:34:04 2001 UTC (23 years, 4 months ago) by tdb
Branch: MAIN
Changes since 1.2: +10 -4 lines
Diff to previous 1.2

A bit of error handling. If the client closes "uncleanly" we get this exception
thrown my JacORB.

Just a mental reminder really.... this class isn't finished :)

Revision 1.1 - (view) (annotate) - [select for diffs]
Mon Feb 5 00:58:46 2001 UTC (23 years, 4 months ago) by tdb
Branch: MAIN

The original "all in one" class didn't work quite right, so it's been broken
down into two classes; one for control, and one for sending data. The whole lot
functions in a very similar way to the TCP setup, except that communication
happens over CORBA.