Network Printing Requirements
Charles Bazaar <cbazaar@emulex.com> Fri, 24 July 1992 19:09 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa07854; 24 Jul 92 15:09 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa07850; 24 Jul 92 15:09 EDT
Received: from inet-gw-2.pa.dec.com by NRI.Reston.VA.US id aa29241; 24 Jul 92 15:09 EDT
Received: by inet-gw-2.pa.dec.com; id AA29714; Fri, 24 Jul 92 12:09:00 -0700
Received: by nsl.pa.dec.com; id AA14765; Fri, 24 Jul 92 11:56:07 -0700
Received: by nsl.pa.dec.com; id AA14761; Fri, 24 Jul 92 11:56:04 -0700
Received: by inet-gw-2.pa.dec.com; id AA28954; Fri, 24 Jul 92 11:56:02 -0700
Received: by emulex.emulex.com id AA06618 (5.64+/IDA-1.3.4 for print-wg@Pa.dec.com); Fri, 24 Jul 92 11:57:59 -0700
Date: Fri, 24 Jul 1992 11:57:59 -0700
From: Charles Bazaar <cbazaar@emulex.com>
Message-Id: <9207241857.AA06618@emulex.emulex.com>
To: print-wg@pa.dec.com
Subject: Network Printing Requirements
Resourse pour clients are important to us, but just as important is status information. Most current spooling implementations (lpr/lpd for instance) do not take into consideration status information available from the physical device. Much of this is probably due to the inability of the parallel interface to provide returned information. With new bi-directional parallel interface proposals pending, a new lpr/lpd proposal should have the capability to accept and/or query for status info. Of course there remains questions of how this information would be made available to applications (spoolers, word processing pgms, etc.) Charles Bazaar bazaar@emulex.com
- Network Printing Requirements Charles Bazaar
- Re: Network Printing Requirements Brad Clements