-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 2 Jun 2012 18:24:22 -0500 "Christofer C. Bell" <christofer.c.b...@gmail.com> wrote:
[snip] > > That said, there have been a number of suggestions towards modifying > the OP's requirements and I'm interested in seeing the reasoning > behind the requirements themselves. Aubrey hasn't replied yet and I > think there's value in giving her an opportunity to respond, clarify > and perhaps narrow her requirements, and allow us to provide better > advice. The fact is, with the requirements set as they are, there is > no possible solution (see below) to her problem. My reasoning may not be as well-thought-out as I first thought, as pointed out directly and indirectly by many people in this thread. ;) In the end I think I may be using Miles' suggestion of Woof; it is essentially a one-off ad-hoc HTTP server implemented in python. > (Yes, I did see someone suggest nc (possible alternative: socat). > While that *does* meet the OP's initial set of requirements, that's > not really much of a "solution"...) ;-) > Surprisingly netcat might very well be a perfectly reasonable way to go... I will look into socat while I'm at it, thank you. - -- Aubrey "There are two types of people in the world: those who can extrapolate from incomplete data." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJPyy7kAAoJEDqgFXa7UFQObaYIAJaqWDDXgC08ISzs3jKTKV0W y5EQaTzMNdQ7/32zxKtmj+HGdlInYcqpp9Dv6+EHSv4wuzLVDD0hZIApP2MHXXY6 mm4gT1Nv5dG6/ITzh0JU1H+CedCeJbBm2mTDmCn/JhSSnYlc2zwLxkdoHH//Cbx9 F+DwoBSNRjoHj761zoj391wyZncj0fiDqF+Uosr0Ce0D0y4RQ+blTXObvus2uIWe eUNto+3F+FwIZFtj3xsMm8A88gVXIYYrtsHGvpfBqTBiRu0UH0OrECOuWArkEoqI oimG2Z/7ry3Ium8nqPdJf68gEIiyHQk9WcqQHIXpadWQwgYqSkB3AwvaHBETISI= =QB21 -----END PGP SIGNATURE-----
