> Anyway,with the pause in place I later get funky results from
> SocketStream>>upTo:. Your SocketSteam is obviously not "compatible" with
> the one in Comanche. I have code that does this:
> 
> getResponse
> 	"Get the next line from the server."
> 	| nextLine |
> 	nextLine _ stream upTo: Character lf.
> 	stream next.
> 	^nextLine

the stream next shouldn't be there, "standard" upTo: semantic is to skip 
the delimiter:

Answer a subcollection from the current access position to the
	occurrence (if any, but not inclusive) of anObject

> ...and this seems to result in a String with 10 LFs in it. Hmmm, haven't
> looked deeper here so I can't give more feedback right now.

Hmm, are using the stream as binary or ascii?

Michael