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?

Jim Walker (walker@dazel.com)
Tue, 09 Sep 1997 15:56:41 -0500

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Robert Herriot: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Previous message: Jim Walker: "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: Robert Herriot: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"

> 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?

Uhhh... I believe that I will leave it as an exercise for the user.
Let's just say that there is a variety of ways that one might do it;
certainly either of the solutions that you hint to above might work.
I could even imagine one or two more.

I do not mean to be too mysterious, but it seems sufficient to me
that there are implementations in the field today that solve a
similar problem.

later...
...walker

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

Next message: Robert Herriot: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"
Previous message: Jim Walker: "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: Robert Herriot: "Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?"