Re: the latest draft, LPR-LPD
leo j mclaughlin iii <ljm@ftp.com> Mon, 16 March 1992 20:22 UTC
Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa00244; 16 Mar 92 15:22 EST
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa04933; 16 Mar 92 15:23 EST
Received: from inet-gw-1.pa.dec.com by NRI.Reston.VA.US id aa04929; 16 Mar 92 15:23 EST
Received: by inet-gw-1.pa.dec.com; id AA21107; Mon, 16 Mar 92 12:24:07 -0800
Received: by nsl.pa.dec.com; id AA00573; Mon, 16 Mar 92 11:36:15 -0800
Received: by nsl.pa.dec.com; id AA00567; Mon, 16 Mar 92 11:35:59 -0800
Received: by inet-gw-1.pa.dec.com; id AA18052; Mon, 16 Mar 92 11:35:39 -0800
Received: from ljm.leather-lace.ftp.com by ftp.com via PCMAIL with DMSP id AA29926; Mon, 16 Mar 92 14:36:31 -0500
Date: Mon, 16 Mar 1992 14:36:31 -0500
Message-Id: <9203161936.AA29926@ftp.com>
To: trewitt@pa.dec.com
Subject: Re: the latest draft, LPR-LPD
From: leo j mclaughlin iii <ljm@ftp.com>
Reply-To: ljm@ftp.com
Cc: joel@ftp.com, print-wg@pa.dec.com, trewitt@pa.dec.com
Sender: ljm@ftp.com
Repository: babyoil.ftp.com
Originating-Client: leather-lace.ftp.com
> >The reason for the new send* commands was to allow interoperability >with old agents. With 1179, there was no way for an agent to >communicate with a daemon and determine whether it was safe to use the >"extensions" specified in 1179.... > Well...if you have an only new client and an only old server the failure mode in both 1179 and the new RFC is the same -- you can't print. The advantage of the draft mechanism is that unlike 1179 clients, the new specification allows for draft clients to dynamically adapt to old or new servers. > >1179 is completely broken, as far as interoperability goes. The new >RFC does not allow the 0-length encoding or any other changes to the >semantics of the existing commands. > Then the new RFC is even more broken as far as interoperability goes. If the number of email messages I have recieved asking questions about 1179 is any indication, a lot of folk out there have implemented 1179 compliant lpr clients. For the new RFC to break these existing implementations is a rather large departure from normal protocol development. enjoy, leo j mclaughlin iii ljm@ftp.com
- the latest draft, LPR-LPD Joel Gartland
- Re: the latest draft, LPR-LPD Glenn Trewitt
- Re: the latest draft, LPR-LPD leo j mclaughlin iii
- Re: the latest draft, LPR-LPD Bruce Crabill
- Re: the latest draft, LPR-LPD leo j mclaughlin iii
- Re: the latest draft, LPR-LPD Bruce Crabill
- Re: the latest draft, LPR-LPD Glenn Trewitt