Modify RFBSocket class >> #acceptFrom: to read:

super new works for Socket, since it avoids calling the actual #new implementation in Socket, same is not true its subclasses call super�

Note to tracker:

Might be a good idea to "bulletproof" Socket>>acceptFrom:, by either

1) having it unregister existing handle/semaphores (The "I hope you weren't using that!" approach), or 

2) raise an error in that case. (The "Surely you jest, madame?" approach)

As someone rarely using sockets, I would prefer 2 but have no strong opinion on the matter, what do the rest of you think?

Cheers,

Henry