Re: Preserving object props on sockets

> Thanks for testing.=A0 Latest iteration now is rebased on the support
> for server and servertype smobs.=A0 (That support is necessary in order to
> justify the removal of svz:server:state-{ref,set!} (after rewriting the
> mandel and icecast servers to use object properties, of course).)
> =

> Rumninations follow; feel free to ignore.
> =

> Anyway, the remaining design worry is that to manage socket smobs in the
> same way, libserveez needs to add a pre-finalization hook for sockets so
> that guile-server can specify a function to invalidate the SMOB/C-object
> coupling.=A0 Adding the the libserveez API is not an immediate problem,
> actually -- the doubt lies w/ whether or not such extension is a one-off
> decision, or something that will recur (w/ other types).=A0 If the latter
> is possible, then maybe there are different ways to design the change in
> API so that is (will be) less hodge-podge.=A0 The primary impact for any
> libserveez change in this area is for wrapping code (such as for Guile).

At the risk of saying something poorly thought out... for the
pre-finalization, you might be able to have that occur in the
SMOB mark procedure (?).