IPP> HTTP transport for IPP

IPP> HTTP transport for IPP

IPP> HTTP transport for IPP

Robert Herriot Robert.Herriot at Eng.Sun.COM
Thu Apr 10 15:12:09 EDT 1997


> From harryl at us.ibm.com Wed Apr  9 15:45:34 1997


> 1. The idea of returning 3 URL (Data, Status, Modify) upon job submission is an
> excellent means of facilitating end-user job status and ability to cancel one's
> job. However, sometimes there may be an administrative application that wants
> to modify jobs. Unless this application had also received the Modify URL, it
> would be unable to cancel or modify jobs in the "IPP queue".
> 
> I think this might be accomplished by a QUERY to the "root" IPP service URL
> which would return a list of currently active and pending print jobs. It would
> be crucial that, included with this list would be the Modify URLs. Note there
> may need to be some authentication regarding who gets these.
> 
> 


I think that I understand the reasons for having 3 URLs returned, but
I still keep thinking that 1 job URL would be better and simpler.  


Harry's example above reminds me of this problem when he mentions that
the list of jobs returned should include at least two job URLs for each job
(i.e. the query url and the modify url).


We may also decide to add more URLs later and have different URLs for
cancel and for modify, giving us 4 job urls.


Does anyone else think that we should strive for one job URL, and have
the operation specified in the message, or am I alone?


Bob Herriot



More information about the Ipp mailing list