Here are some thoughts on how HTTP could be extended for the user printing
functions for the Internet Printing Protocol (IPP) project.
>Return-Path: <majordomo at cp10.es.xerox.com>
>To: xerox-ldpa at cp10.es.xerox.com>Subject: Re: Alternative Languages and Encoding for LDPA
>From: Larry Masinter <masinter at parc.xerox.com>
>Date: Tue, 5 Nov 1996 13:29:12 PST
>>It's interesting to look at the HTTP/1.1 specification for the large
>number of places where things senders might send must be ignored.
>>I know Bill Janssen is working on a paper on extensibility in Internet
>protocols, and it's an interesting subject.
>>># What would help is to have a specific proposal of how to extend
># HTTP to have the following DPA/LDPA operations:
>>This is similar to the discussion we're having in the "Distributed
>Authoring and Versioning" group, which is trying to build a profile
>for doing document management at web sites (e.g., such as FrontPage,
>MKS Source Integrity, Documentum, etc. are doing). In that group, as
>here, the issue is: New methods, or POST with new content?
> You might want to look at the home page for that working group:
>>http://www.ics.uci.edu/~ejw/versioning/>>We have good participation from Xerox in this group, and the
>possibilities of converging DMA functionality and the web looks good.
>>SubmitJob could easily be a POST which returns a job attributes and a
>Location: header that is the Job URL. CancelJob could be done with a
>DELETE of the Job URL, ListJobAttributes might be GET of the Job URL,
>ModifyJob could be a PUT of the Job URL with a new set of Job
>Attributes (or Post). I don't know what ResubmitJob might be, but
>perhaps it's a POST too.