-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Micah Cowan wrote: > For my part, I see something which, at least for first cut, I could whip > up in a couple of hours (the server emulation and associated > state-tracking, of course, would be _quite_ a bit more work). What is it > that causes our two perspectives to differ so wildly?
Perhaps it's that we're both missing the fact that we already have exactly what I'm talking about: connect.c. That's exactly what I was proposing, but somehow I missed that we were already using an interface between ourselves and the Berkeley Sockets API. It would probably need slightly more abstraction to be suitable for SOCKS (in particular, it'd need to be object-based, so some connections use plain TCP connections while others might use SOCKS); but in the meantime, the emulated server I mentioned could be swapped in for tests as simply as linking against server-emu.o instead of connect.o. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH+K6e7M8hyUobTrERAhg8AJ4wsD1x4RgW92Fzx1ilLmQ2wi0CeQCdG7rC eE8NoOmbeOMRAZ//OY3zVmM= =42Fk -----END PGP SIGNATURE-----
