Re: Preserving object props on sockets

> Too, i realized that not only "socket" smobs are affected by the

> cons-on-demand approach, but also "server" and "servertype" =

> objects.
> =

> So, back to the drawing board...=A0 please see:
> =

> http://git.savannah.gnu.org/cgit/serveez.git/commit/?h=3Dq-prec-smob
> =


TTN-

So to test it, I resurrected a Serveez TFTP server I once started.
It makes a good test since, in TFTP, a new ephemeral server port
is opened for each connection.=A0 So it makes sense to attach state
to each server socket.

I haven't checked your implementation, but, AFAICT, obj props
on sockets works as expected.

If that code ever reaches a non-embarassing state, I'll post it
somewhere.

Thanks,

Mike