Re: q-ears

--===============5382426044181398924==
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]>
() Fri, 15 Nov 2013 14:02:12 +0100

   [...] added member =E2=80=98svz_array_t *ears=E2=80=99 and converted lib=
serveez to
   maintain the bindings array there.  Does this look OK?  Anything
   obviously wrong jump out to the authors/experts?

Thunderous silence!  What does that mean?  (Nothing means nothing!)

Anyway, rather than burn another word per socket, i've decided to use a
hash table, in the process adding "socket property" funcs as well.  See:

 http://git.savannah.gnu.org/cgit/serveez.git?h=3Dq-soprop-ears

for details.  For now, the soprop funcs are "internal" (for libserveez
use only), but maybe they will eventually find their way into the API.

Next up -- i think the last remaining misuse of =E2=80=98svz_socket_t.data=
=E2=80=99 is
in the coservers.  We can probably use soprops for that, too...

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

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

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

iEYEARECAAYFAlKVwesACgkQZwMiJEyAdQIPYwCg3tFlmkUjgvjkoIuF4uo79gn0
uUoAnAyLfl8Y/IWp6Jd8+4jZ/LWYXSRq
=7X6v
-----END PGP SIGNATURE-----
--=-=-=--


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

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

--===============5382426044181398924==--