IPP> Re: IPP> REG - Proposal for "job-recipient-name" Job Tem plate attribute

IPP> Re: IPP> REG - Proposal for "job-recipient-name" Job Tem plate attribute

IPP> Re: IPP> REG - Proposal for "job-recipient-name" Job Tem plate attribute

Hastings, Tom N hastings at cp10.es.xerox.com
Thu Sep 21 13:31:07 EDT 2000


Are you guys talking about receipt of event notifications or receipt of the
printed job output indicated as a Job object attribute and banner page text?

If event notifications, what events (job held or job completed or what?) and
how is the event specified?  Hopefully in some Per-Printer or Per-Job
Subscription.

Tom



-----Original Message-----
From: Michael Sweet [mailto:mike at easysw.com]
Sent: Thursday, September 21, 2000 06:18
To: McDonald, Ira
Cc: Hastings, Tom N; ipp (E-mail); QUALDOCS DL (E-mail)
Subject: Re: IFX> Re: IPP> REG - Proposal for "job-recipient-name" Job
Template attribute


"McDonald, Ira" wrote:
> 
> Hi Mike,
> 
> Here's a way to have our cake and eat it.
> 
> The attribute 'job-recipient-name' is specified to be
> a person's full name, network user name, or whatever
> name's descriptive to humans (but NOT meant to be
> parsed by automated software).
> 
> A different attribute 'job-recipient-role' could hold
> 'none', 'operator', 'admin', 'technician', etc. for
> jobs that need to reach someone who fills a particular
> role in the local network environment.  If the attribute
> type was (keyword | name) then we could also let users
> specify roles like 'accounting', 'payroll', etc.

Now *that's* a good idea! :)

I'd only ammend this to add an empty job-recipient-name attribute
means that the actual recipient is unknown, and a member of the
job-recipient-role attribute should be used instead.

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products                  mike at easysw.com
Printing Software for UNIX                       http://www.easysw.com



More information about the Ipp mailing list