[Consmgr-tech] Connector/Listener implementation

[Chris R. <cro...@di...>]

  Hey there.  Okay, I'm still having a pretty big problem understanding
what's in the architecture document.  Unfortuntely the "add new
information on the bottom" has left it internally inconsistent.  Made
even more complicated by the class renaming.

  Could you please coalasce the section that starts "Listener Redesign"
with the one that starts "One More Step[...]" ?  The information in the
former of those two sections is I think mostly unimportant, if not
actually incorrect in places, given the later redesign described in the
last section.

  The problem I'm having now is that I'm not sure how everything fits
together.  The little descriptions of each class heirarchy and its
presumed functional responsibilities (that is under the earlier
"Listener Redesign" section) is just what I need, but I need it for the
new system where Listeners are one thing, and Connectors are another.
Particularly, the information about Connectors up in that earlier
section still suggest that a Connector (subclass) should have
information and functionality about incoming connections, but I believe
this is no longer true, correct?

  Does Connector still have information about how to establish a
connection, *and* information about how to read and write on the
connection after it is established?  So, we need a "are we connected"
boolean (which I think is already there, pulled from
Connection/Outlet/BiDirConn)

 Thanks.  I think that bit of redocumenting will help me a lot.  And, if
you're going to have time to work on the code, I'm happy to just let you
do that to finish that refactoring.  Things are a mess right now, and
I'm inclined to work on it, but it's clearly a bit easier for you since
you started, and have a better idea what should be where in concept than
I do right now.

  Thanks...

                           - Chris