Sven Van Caekenberghe wrote > > Most socket API's allow for the creation of a server socket on the next > available port, often by specifying 0 instead of a port. When the socket > is bound, one can retrieve the local port and let the client(s) know. I > tried to do that in Pharo today, and these steps seem to work, by > accepting an incoming connection gives a primitive failed. > > socket listenOn: 0. >
I would say that: socket listen. would be nicer interface than giving special meaning to number 0 in this context. Davorin Rusevljan ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/Socket-listenOn-0-accept-tp4459813p4477991.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
