--kU1KBl72y3ES5hCz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Sep 08, 2003 at 12:25:18PM -0400,
elemint@cox.net wrote:
> Would a recieve only cable be a good idea so the server on a seperate
> nic would have a cable where it could recieve only recieve the
> updated files and then implement them?
Not a good idea -- you really need two-way communication for any
standard TCP-based protocol to work. (If the other server can't
respond, how can it complete the three-way handshake, for example?)
I suppose you could go the UDP route and use something like TFTP, but
you'll be left without error correction.
--=20
Bill Jonas * bill@billjonas.com * http://www.billjonas.com/
"It's a dangerous business, Frodo, going out your front door. You step
into the Road, and if you don't keep your feet, there is no knowing
where you might be swept off to." -- Bilbo Baggins
--kU1KBl72y3ES5hCz
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE/XLJ3dmHcUxFvDL0RAgRlAJsG4MbTj1nl3+Y+PNPjnuiGWQBBZACfWf3I
xl3QYbLJWOznsHvlHrr7mAw=
=dksi
-----END PGP SIGNATURE-----
--kU1KBl72y3ES5hCz--
(text/plain)