[Q] What is the status of the "network rewrite?"
Chris Muller
afunkyobject at yahoo.com
Wed Aug 27 23:39:02 UTC 2003
> The low level interface to Socket hasn't changed that much in the
> rewrite. You can see the difference by comparing the ocde in OldSocket
> and Socket. You may also want to consider using SocketStream to put a
> stram abstraction between your server code and the network/Socket
> communication.
Hi Michael, thanks for your prompt reply. The first thing I did was compare
OldSocket to Socket and I noticed an implementation difference other than API.
OldSocket>>waitForAcceptUntil: appears to have been renamed in
Socket>>waitForAcceptFor:. However, the new method does not return the new
socket instance which is a critical bug, I think.
So I guess what I'm really trying to figure out is, is there work still being
done on Socket? If not, I would expect that such a critical class would have
been well regression tested. If so, I may hold off on porting my code.
Is Socket good to go? Can I port my code to the new Socket API, or should I
wait?
Thanks,
Chris
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
More information about the Squeak-dev
mailing list
|