q-ears

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

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

In libserveez, =E2=80=98svz_socket_t=E2=80=99 has member =E2=80=98void *dat=
a=E2=80=99, which is terribly
ambiguous and (apparently) easy to confuse and abuse.  I think it should
be strictly for the servers to use and not touched by libserveez at all.
However, that's just one programmer's opinion, and one who was not in on
the original design discussion.

To try to achieve this, i've added member =E2=80=98svz_array_t *ears=E2=80=
=99:

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

and converted libserveez to maintain the bindings array there.  Does
this look OK?  Anything obviously wrong jump out to the authors/experts?

=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)

iEYEARECAAYFAlKGG1gACgkQZwMiJEyAdQKntwCfWzPbWUu4cwFtU9KkcYDN3KdM
O9UAnRv43om7Nt5hOVRwoqb9k52Ssbx1
=TR3E
-----END PGP SIGNATURE-----
--=-=-=--


--===============2993273417597091625==
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

--===============2993273417597091625==--