IPP>NOT mailto feature from IETF meeting (RE: IPP> ADM - TheIPPNotification I-Ds will now go the IESG)]

IPP>NOT mailto feature from IETF meeting (RE: IPP> ADM - TheIPPNotification I-Ds will now go the IESG)]

David_Kellerman at nls.com David_Kellerman at nls.com
Thu Aug 17 14:47:59 EDT 2000


Carl,

> The problem with polling (with Get-Job-Attributes) is that many Printers
> forget about a Job as soon as it has reached a final state:  completed,
> aborted, or canceled.  So, on one poll you see the job is in 'processing'
> state, and on the next poll you get 'client-error-not-found', and you have
> no way of knowing what the final state of the Job was before it
> disappeared.

Okay, I'm obviously landing in the middle of a long discussion. 
Apologies if I'm covering old ground. 

What you describe is very, very sad.  Anyone who's worked with
lpr/lpd, and tried to deliver status or completion results has
cursed this deficiency in lpr/lpd -- the completed job vanishes. 
Now here we are 25 years later, and we're propagating the same
shortcoming. 

Moreover, we're trying to patch the problem with
machine-readable e-mail notification?  If this is important (and
it is), let's address the underlying problem. 

And please don't anyone tell me about their $99 printer for
remote internet printing that can't cache a reasonable amount of
completed job status but does have the resources to deliver
multi-part MIME e-mail.  ;-)

David

::  David Kellerman         Northlake Software      503-228-3383
::  david_kellerman at nls.com Portland, Oregon        fax 503-228-5662



More information about the Ipp mailing list
Our website uses cookies on your device to give you the best user experience. By using our website, you agree to the placement of these cookies. To learn more, read our privacy policy. Read Privacy Policy