IPP Mail Archive: Re: IPP> HTTP transport for IPP

Re: IPP> HTTP transport for IPP

Jim Walker (walker@dazel.com)
Thu, 10 Apr 1997 15:32:27 -0500

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Randy Turner: "IPP> Protocol Definition"
Previous message: Randy Turner: "Re: IPP> HTTP transport for IPP"
Maybe in reply to: Harry Lewis: "IPP> HTTP transport for IPP"
Next in thread: Harry Lewis: "Re: IPP> HTTP transport for IPP"

Robert Herriot wrote:
>
> 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?

I, for one, would prefer a single URL as well...
...walker

--
Jim Walker <walker@dazel.com>
System Architect/DAZEL Wizard
DAZEL Corporation, Austin, TX

Next message: Randy Turner: "IPP> Protocol Definition"
Previous message: Randy Turner: "Re: IPP> HTTP transport for IPP"
Maybe in reply to: Harry Lewis: "IPP> HTTP transport for IPP"
Next in thread: Harry Lewis: "Re: IPP> HTTP transport for IPP"