IPP> machine readable etc. - why Harry is right

IPP> machine readable etc. - why Harry is right

IPP> machine readable etc. - why Harry is right

Carl Kugler/Boulder/IBM kugler at us.ibm.com
Tue Aug 22 16:54:43 EDT 2000


"Herriot, Robert" <Robert.Herriot at pahv.xerox.com> wrote:

>
>> -----Original Message-----
>> From: Carl Kugler/Boulder/IBM [mailto:kugler at us.ibm.com]
>> Sent: Tuesday, August 22, 2000 12:52 PM
>> For
>> example, you do a Print-Job request, and get back a chunked
>> response.  The
>> first chunk contains the normal Print-Job response.  Additional chunks
>> follow (later), containing notifications about the job
>> progress.  This is
>> efficient enough for page-by-page notifications.
>
>But would the chunks be so conveniently divided in an off-the-shelf web
>server?

Well, I don't know of any off-the-shelf web server that supports IPP.  So
then it's going to depend on the IPP implementation and the server APIs:
CGI, Servlet, NSAPI, ISAPI, whatever.  Those APIs that support chunked
responses tend to emit a chunk for each write() on the API, so the IPP
implementation could divide up the chunks this way.  It doesn't really
matter too much though.  You might see some "jitter" in the timing of the
notification deliveries.  Worst case, with the buffering proxy, you get the
entire Job history in one big blob.

     -Carl




More information about the Ipp mailing list