> From walker at 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?