Re: Preserving object props on sockets

--===============6301400935259060349==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

() Thien-Thi Nguyen <[email protected]>
() Mon, 25 Mar 2013 14:56:47 +0100

   The ugly news is that there are more bugs (see t008) so the lightning
   release i was planning is not going to happen quite like that.  You can
   monitor =E2=80=98q-udp-userdata=E2=80=99 (NB: may undergo rebase) in the=
 meantime.

I just updated branch =E2=80=98q-udp-userdata=E2=80=99, which avoids addres=
sing the
=E2=80=98svz:sock:data=E2=80=99 problem and instead reworks the smob wrappi=
ng for
=E2=80=98svz_socket_t *=E2=80=99, using a cache.  As w/ all caches, the tri=
cky part is
the invalidation protocol, which differs between TCP (do "make check
VERBOSE=3D1" and grep for ZOW in t003.log) and UDP (t008, which is btw not
in Makefile,am -- you have to do "make check TESTS=3Dt008" manually).

This is a roundabout way of saying that there is now a gc assurance bug
to fix, in addition to the others found thus far.  (But t008 passes. :-D)=20

=2D-=20
Thien-Thi Nguyen
GPG key: 4C807502

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlF3ZjUACgkQZwMiJEyAdQJWFwCgk8zNdCb924yFS8QU66fpQ1PG
ePAAoOklVpDkAYENRGQgN8eNvuiJtZ4v
=ipUK
-----END PGP SIGNATURE-----
--=-=-=--


--===============6301400935259060349==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
bug-serveez mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-serveez

--===============6301400935259060349==--