problem with sockets

Jeffrey Chapman dahuang at geocities.com
Sat Dec 19 22:22:13 UTC 1998


 
>> It's true, Squeak is broken in this respect. I don't know why they did
>> not implement the much more common and reliable Berkeley Socket
>> semantics with listen() and accept(),
>> where the underlying OS does the connection queue stuff. Implementing
>> these semantics on top of a weird socket interface such as that of the
>> Mac should be mucht easier than the implementing a reliable server on
>> top of a conceptually broken API...

For quite a while now, the Mac is using STREAMS. Same thing as Solaris, 
if I'm not mistaken... the old MacTCP API is still in place for 
compatibility's sake. I haven't investigated, but is Squeak using that 
older API? OpenStep-based MacOS flavors, FWIW, will have Berkeley Sockets 
and a STREAMS compatibility layer. I've seen various servers ported from 
Unix that implement listen()/accept() on MacOS. Maybe something similar 
could be done in Squeak?





More information about the Squeak-dev mailing list