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)
Tue, 9 Sep 1997 13:45:52 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Jim Walker: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Previous message: Robert Herriot: "Re: IPP> Job-URI vs. Job-Id: How would you handle moving jobs?"
Maybe in reply to: Roger K Debry: "IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Next in thread: Jim Walker: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"

> From walker@dazel.com Tue Sep 9 13:37:45 1997
>
> We have a gateway
> that has been in existence for four years now that solves this
> exact problem: it maps from the LPD job identifiers to an opaque
> printer-independent job identifier.
>
> And folks, it wasn't that hard to do.

Can you give a few details? Do you maintain a mapping table? If so,
what triggers the removal of entries? Or do you use an extended attribute
in the print job to hold the mapping?

Bob Herriot

Next message: Jim Walker: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Previous message: Robert Herriot: "Re: IPP> Job-URI vs. Job-Id: How would you handle moving jobs?"
Maybe in reply to: Roger K Debry: "IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Next in thread: Jim Walker: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"