Sat Nov 22 11:01:44 CET 2008

host + client

So, what's the workflow for having both a client and a host
communicating, instead of an emulated console?

The whole deal with 'lazy connection' never really worked properly..
Time to fix it or get rid of it.  What about: one namespace per
target, so store the connection in the namespace?

Let's simplify.

* The tethered.ss code is parameterized by 'target-in' and
  'target-out', so it doesn't care if the port is a channel or a
  scheme port.

* Lazy connections are not necessary.  If there is no console, the
  target simulator is run instead.