The first incarnation of SocketStream was in Comanche, but the one in
3.7 is a rewrite of it from Michael Rueger.
Later versions of Comanche, currently named KomHttpServer uses the one
now in 3.7.

> I'm still learning about the new stuff: SocketStream and the Server
> classes.  It appears that SocketStream is not a substitute for
> Socket in that you can't "listen" on a SocketStream.  Also,
> SocketStream does not support #store, #skipTo: and other protocol
> assumed by Smalltalk serialization code.  I'm not sure whether to
> code around this or extend SocketStream.
I would probably look into extending SocketStream since it IMHO should
be able to work as a Stream as much as possible.
Just my gut feeling. And since it is pretty new it can surely be
missing things.
For making servers, promise me to take a look at KomHttpServer - there
is a lot of good stuff in there! :)
Gö

KomServices in particular makes writing and managing typical socket
servers very simple.  I'd still like to see this (minus the
DynamicBindings stuff) included in the base Network package.  I can't
remember if Julian or I ended up actually submitting an ENH for this
or not.
Avi