Hi!
Jon Hylands wrote:
"SS can not be run unbuffered, since that seems unneeded. The option to autoFlush is still available, with it set to true SocketStream (just like OSS) will flush on its own on each nextPut:/nextPutAll:, otherwise flushing it will have to be done manually but is done on close."
This is incorrect, as it turns out - what really happens when autoFlush is set to true is that a flush is sent when the outgoing buffer is full, which, as it turns out, is a 4KB buffer. So, this problem was actually on the client side rather than the server side, and was easily fixed by using nextPutAllFlush: instead of nextPutAll:
Right, sorry for the confusion. We should fix so that it behaves like the class comment says I think. I presume people either want it "super auto" or "manual", not "almost auto" :)
Thanks again to Göran for his help in this...
No problem!
regards, Göran