Re: Preserving object props on sockets

> After much thought, i've decided that it is best to explicitly NOT

> support object properties on UDP and ICMP (generally, connectionless)
> sockets.=A0 This is motivated partly by implementation difficulty and
> partly by philosophical considerations (i.e., does "object identity"
> make sense for such a socket, and if so, could it be possible that
> the meaning may be application-dependent?).
> =

> I think if the information of interest for the client code is the remote
> address (for instance) of a connectionless socket, the client code
> should be responsible for extracting that from the socket object and
> stick it in a hash table (or whatever), directly.
> =

> Does that sound reasonable?

Works for me.