Michael,
Now I'm more confused. The purpose of "job-recipient-name" was NOT
notification, but indicating who was the intended recipient of the hardcopy
produced by a job when the intended recipient is different than the
submitting user. In other words, a way to help get the hard copy to the
intended recipient (singular). There are all sorts of ways this could
actually happen (all outside the scope of the standard):
all recipients look through a single pile for their stuff looking for their
name on the banner sheet
people file job output in mail boxes labeled with recipient names according
to the recipient name on the banner sheet
the operator hand delivers output to folks' desks according to the recipient
name on the banner sheet.
etc.
Tom
-----Original Message-----
From: Michael Sweet [mailto:mike@easysw.com]
Sent: Wednesday, September 13, 2000 12:37
To: Hastings, Tom N
Cc: ipp (E-mail); QUALDOCS DL (E-mail)
Subject: Re: IPP> REG - Proposal for "job-recipient-name" Job Template
attribute
"Hastings, Tom N" wrote:
>
> Michael,
>
> I don't understand the idea of adding a keyword. Wouldn't the
> operator or administrator have a name and so would use that name?
The idea is to notify *all* operators or administrators that are
registered on the system.
Some of our customers are reprographics companies - they typically
will have a server controlling a dozen plotters or high-speed
printers, with several operators to keep the show running. Sending
one notification to an operators list is more efficient than sending
N notifications...
Similarly, an office might have several secretaries that handle
incoming faxes; they'll want to be notified when new faxes come
in (and the sender doesn't know the user name for the recipient)
-- ______________________________________________________________________ Michael Sweet, Easy Software Products mike@easysw.com Printing Software for UNIX http://www.easysw.com
This archive was generated by hypermail 2b29 : Wed Sep 13 2000 - 23:45:07 EDT