I personally feel that the Job-URL (sic) is the *only* way to go.
specific printer is immediately broken. The existing URL model
can be supported in my existing client environment, whereas the
proposed <printer-URL, job-ID> model would be a severe obstacle.
In our environment, a job is an object in and of itself; it may
be easily moved from one printer to another.
Jim Walker <walker at dazel.com>
System Architect/DAZEL Wizard
DAZEL Corporation, Austin, TX