IPP>PRO another reason for needing byterange and documen

IPP>PRO another reason for needing byterange and documen

IPP>PRO another reason for needing byterange and documen

Roger K Debry rdebry at us.ibm.com
Mon May 12 09:23:03 EDT 1997


The normal meaning of checkpointing is that the client determines the
boundaries upon which it will restart. It then must organize the data to be
sent on those boundaries.  Boundaries are arbitrary.


Roger K deBry
Senior Techncial Staff Member
Architecture and Technology
IBM Printing Systems
email: rdebry at us.ibm.com
phone: 1-303-924-4080




---------------------- Forwarded by Roger K Debry/Boulder/IBM on 05/12/97 07:07
AM ---------------------------


        ipp-owner @ pwg.org
        05/10/97 07:13 PM
Please respond to ipp-owner at pwg.org @ internet




To: Robert.Herriot @ Eng.Sun.COM @ internet, jkm @ underscore.com @ internet
cc: ipp @ pwg.org @ internet
Subject: Re: IPP>PRO another reason for needing byterange and documen


At 11:10 PM 5/9/97 -0400, JK Martin wrote:
>Is IPP expected to support checkpointing to the point where the
>client will resume submission of document at *precisely* the point
>where the transmission failed?
>
>I wouldn't think so.  Rather, the client would resume transmission
>at the *start* of the document that failed.
>
>Is this true?
>
> ...jay
>


Jay,


starting over from the beginning is not checkpointing in my book.
The whole point of checkpointing is so that you do not have to
start a big transmission over again from the beginning.


Carl-Uno



More information about the Ipp mailing list