Known problems and limitations in the AAFID2 prototype

All these issues are in our "to do" list, and will be addressed
gradually.

- If a transceiver dies abnormally and the monitor (and the GUI) does
  not find out about it, when you try to exit the GUI, it will wait
  for all the transceivers to finish, but the one that died will never
  send the DISCONNECT signal, and the GUI will wait forever. In this
  cases, you have to kill the GUI by hand (CTRL-C or kill) when only
  the icon for the transceiver that will not die remains.

- The GUI does not support starting new Monitors in other hosts to
  create a hierarchical structure. This can be done using the
  text-based interface, however.

- There is no way to specify processing code to be executed in the
  transceivers or the monitors to do data reduction.

  In fact, there is no data reduction at all, yet.

- Error handling is flaky.

- There is no security in the communication mechanisms.

- The inter-host communication mechanism is TCP, which may be too
  resource-intensive for large installations.
