Lic. Edgar J. De Cleene wrote:
> Well, I use this without problem for a long time on OS X and OS 9 and
> Windows.
> So , when some squeakers send notice about rip OldSocket from image , others
> send mail about keep all examples in this class (and update to Socket).
> Me too and send the blamed methods as Socket.2.cs  telling what still are
> needed , and at my surprise in a few days I see as infamous 6366 update with
> my name .
> So , suppose I was guilty .

No, no, I didn't mean to imply this. It shouldn't have gotten into the 
stream, but it is partly my fault because I missed the discussion about 
the socket stuff, only found it when I searched backwards in the list.

> But wish some more experience guy tell me what are the exact equivalents to
> all methods and the exact problems for keeping .

It would be helpful to port the class side methods of OldSocket to 
Socket. By port I mean change them so they work with the existing 
Socket, not OldSocket protocol.

> By the way the sendObject and getObject belongs to Diego Gomez Deck from his
> rST, and I use in network games.

Those shouldn't be in Socket, maybe in SocketStream, or IMHO part of 
your application's communication code. Serializing objects in a generic 
way should be used with caution.

> To bad I just loss my 6366 share of Squeak and almost 1 million value.

No loss, you raised an important point! Please don't feel rejected :-)

Cheers

Michael