Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!caen!math.lsa.umich.edu!math.lsa.umich.edu!emv
From: tcs@BRL.MIL (Terry Slattery, SECAD)
Newsgroups: comp.archives
Subject: [tcp-ip] Re:  sockets vs. streams
Message-ID: <1990Sep10.154118.7257@math.lsa.umich.edu>
Date: 10 Sep 90 15:41:18 GMT
Sender: emv@math.lsa.umich.edu (Edward Vielmetti)
Reply-To: tcs@BRL.MIL (Terry Slattery, SECAD)
Followup-To: comp.protocols.tcp-ip
Organization: The Internet
Lines: 21
Approved: emv@math.lsa.umich.edu (Edward Vielmetti)
X-Original-Newsgroups: comp.protocols.tcp-ip

Archive-name: tcpf/07-Sep-90
Original-posting-by: tcs@BRL.MIL (Terry Slattery, SECAD)
Original-subject: Re:  sockets vs. streams
Archive-site: ftp.cisco.com [131.108.1.27]
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)

> This would be nice.  A possible solution is to write a program "netsend":
>      
>      cat somefile | netsend tcp:x.x.x.x-y.y
> 
> Since printcap allows sending to a filter rather than a specific
> device, the solution is general enough.

But it won't work for a postscript printer being driven from the
Transcript software.  Transcript wants to talk to the printer to
get status info, so the link needs to be bi-directional.

What you suggest has been done by cisco for their terminal servers
and is available from ftp.cisco.com:tcpf.c.

	-tcs