Re: Preserving object props on sockets

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

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

() Mike Gran <[email protected]>
() Sat, 7 Sep 2013 15:07:58 -0700 (PDT)

   > [lameness incarnate]
   > Does that sound reasonable?

   Works for me.

Well, after more thought, i realized how lame that position is and how
as a (Serveez) user i would be disappointed at the (programmer who would
support the) incoherency of a system where some objects are normal and
some are not.

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...  please see:

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

for the current thinking.  The user-visible change is reflected in t008
passing (as before w/ q-socket-objprop), but the DWR items now reflect
different considerations.  Any feedback on those would be most welcome.

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

iEYEARECAAYFAlJvXPkACgkQZwMiJEyAdQJPjQCghwWf8iOJgsuFSMFd/VaWO+3n
nN0AoMiowz4isY/X5bYxwyfnwExEAOeI
=R5R2
-----END PGP SIGNATURE-----
--=-=-=--


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

--===============7541863502781044954==--