Re: [bug-serveez] Preserving object props on sockets

[Thien-Thi Nguyen]

() Thien-Thi Nguyen <address@hidden>
() Wed, 24 Apr 2013 14:40:02 +0200

   See also new branch ‘q-socket-objprop’, which is just ‘q-upd-userdata’
   squashed and refined a bit (more ready for eventual merge to ‘p’).

   Time to do other stuff now; will revisit in a few days...

After much thought, i've decided that it is best to explicitly NOT
support object properties on UDP and ICMP (generally, connectionless)
sockets.  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?

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

pgp1Zl5Ryy4wv.pgp
Description: PGP signature