IPP Mail Archive: Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?

Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?

Robert Herriot (Robert.Herriot@Eng.Sun.COM)
Fri, 5 Sep 1997 14:58:02 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Jay Martin: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Previous message: Robert Herriot: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Maybe in reply to: Roger K Debry: "IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Next in thread: Jay Martin: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"

> From rdebry@us.ibm.com Fri Sep 5 06:16:30 1997
>
> I agree with Jay that this seems like a clean approach. However,
> if I've understood all of the arguments, I thought that dictating the form
> of the URL was a no-no. On the other hand, if a PARTICULAR IMPLEMENTATION,
> such as NT, requires a 32-bit integer job ID to be consistent with its existing
> APIs, then there should be no reason why THAT implementation could not
> use the approach that Jay suggests to easily map to an internal integer job
> identifier.

But Microsoft clients cannot assume that all IPP servers will be
Microsoft servers. Thus the client has no sure way to parse the
Job-URI.

Bob Herriot

Next message: Jay Martin: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Previous message: Robert Herriot: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Maybe in reply to: Roger K Debry: "IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Next in thread: Jay Martin: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"