-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> What if we just factor out a _get_listening_socket() from the serve()
> method?
> It seems like that would give you a reasonable path to follow to implement
> all of this.

Could be an option, although I would like this "unix domain" issue be
solved in standard durus :p.

If I could ask for a beautiful world :-), I would request a "client
factory", that is an object which gives away socket "like" objects when
a client connects. This probably precludes also current "select()"
implementation (should be a external call too). This way I could have
control over the client<->server link. For example, to encrypt
connections transparently, or to use shared memory if both client and
server are in the same machine. Or to integrate Durus is a Twisted
environment (god, I hate twisted a lot!).

That socket "like" object should implement "recv()", "send()",
"sendall()", "close()" and little more, and the internals could be hidden.

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea@argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea@jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRGny3plgi5GaxT1NAQIpuQQAoWyhx7+mLF34UBcL9l3i6vabcuEMNdc9
WvJpx2HU91qEd4LB21r+dDBXVmEl4sRbim7enSQuKqY3cwqWK96P/DZEQyFUifNQ
SeULkQ5sxuZI/eifiOZMeZlENFtz4mpDf+yvdhPzkJZrloqqxGqfIMDmSZbGFrk4
EVtm8Vb9HW8=
=Vqn3
-----END PGP SIGNATURE-----