> From walker at dazel.com Tue Sep 9 13:20:06 1997
>> I can point you to a print system that is in use today that uses
> the concept of an independent job object (akin to a job-URL),
> and it is successful in solving the move-job problem. The job is
> managed independent of the printer, making it very easy to move
> the job, and retain its identity.
In DAZEL does a job have a single invariant identity for the duration
of the job, even if it is moved? If so, does that imply that the
server that acts as the handle for job when it is created continues to act
as this handle throughout the life of the job, and that this server
may or may not be the server for the original printer?