At 03:40 PM 7/2/97 PDT, Daniel Cogswell wrote:
>I've been working on a prototype that uses the IPP and I have run into a
>question which I would be interested in hearing some comments on.
>>I think of HTTP as not being a connection oriented protocol. I know I'm using
>the term loosely here, but, as I understand it, when you open up a connection
>using http you can write and then you can read once. You can't do the
>read/write read/write kind of activity. There is, however, the
CreatePrintJob
>command in IPP which wants to maintain a connection. That is, it wants this
>read/write read/write connection. How does IPP plan to maintain the
connection
>when it begins to append documents to the job?
>>>Dan Cogswell
>http://swan.penn.boulder.ibm.com>
Dan,
this is an addition to the reply you already got back from Randy about HTTP
1.1.
The Create-Job operation, if successful, always returns a job URI. You
will use that URI to post any further documents (Send-Document) or
print-by-reference URIs (Send-URI) that belong to that job, even if you do
it in a new HTTP connection. In effect you will probably have to make it in
a new connection as the job URI is different from the Printer URI, that you
use for the Create-Job.
Carl-Uno
Carl-Uno Manros
Principal Engineer - Advanced Printing Standards - Xerox Corporation
701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
Phone +1-310-333 8273, Fax +1-310-333 5514
Email: manros at cp10.es.xerox.com