[squeak-dev] re: What is the contract of SocketStream>>#next:?

Chris Muller asqueaker at gmail.com
Thu Oct 9 20:03:44 UTC 2014


On Thu, Oct 9, 2014 at 2:20 PM, Craig Latta <craig at netjam.org> wrote:
>
> Chris> I feel I should be able to write:
> Chris>
> Chris> header := mySocketStream next: 4
> Chris>
> Chris> and not have to check the length of header before I access it.
>
> Craig> Yeah, Squeak socket support is broken here (and a lot of other
> Craig> places), I'd say.
>
> Chris> That might be overstating it. I've only ever seen the issue
> Chris> under very heavy load...
>
>      Well, we disagree.

Maybe not, it might help if you elaborated some of the broken places,
I'm probably simply unaware of them.  My apps make very heavy use of
Squeak's Socket with no problems, but last month I upgraded Magma to
use the SocketStream wrapper and only then did I notice this issue
perhaps 2 or 3 times in the last month, and each time when a server
was processing thousands of requests per minute over TCP sockets.


More information about the Squeak-dev mailing list