IPP> About notification [answers to your questions]

IPP> About notification [answers to your questions]

IPP> About notification [answers to your questions]

Hastings, Tom N hastings at cp10.es.xerox.com
Mon Jun 19 17:43:11 EDT 2000


Here are the answers to your questions preceded by TH>.

Tom, Bob, and Hugo

-----Original Message-----
From: Vinod P N [mailto:vinodpn at teil.soft.net] 
Sent: Thursday, June 08, 2000 07:06
To: ipp at pwg.org
Subject: IPP> About notification

Hello all,
	Could someone please clarify these doubts pertaining to
Notification operations:

	1>In the Print-job request, does the sequence in which Job
template attributes and Subscription attributes occur matter?

TH>  The Subscription Attribute Group MUST come after the Job Attribute
Group, since all operations indicate the order that groups MUST be sent.

	2>I have understood the following attributes in Send-Notification
request [indp: delivery method] to be mandatory. Are these correct?

TH> Yes, except as noted.

	Group1: Operation attributes:    attribute-charset

	Group2 to N:Notification attributes:
TH> In order to be consistent with Subscription object names and to not have
duplicate attribute names in two different objects, we agreed to put a
"notify-" prefix on this attribute making it: "notify-printer-uri" for both
the Subscription object and what is sent in the Event Notification content
(for INDP).  

TH> We agreed to rename this: "notify-trigger-event" so that all Event
Notification content attributes start with "notify-", unless they are copied
from some other object (other than the Subscription object).

TH> The 3 above are only for job events.
TH> And "job-impressions-completed" is MUST for 'job-completed' and
'job-progress' events
TH> The 3 above are only for printer events.

	Kindly let me know if there is any attribute missing/redundant.

TH> If the Subscribing client supplied notify-user-data (octetString(63))
you MUST send:                notify-user-data

TH> There are also the following RECOMMENDED and OPTIONAL attributes for the
Notification Source to support in the Send-Notifications content:

                              notify-text          RECOMMENDED
                              notify-sequence-id   RECOMMENDED
                              printer-current-time REQUIRED if you support

TH> Also if the Printer implementation supports the OPTIONAL
"notify-requested-attributes" Subscription Template attribute, then the
Printer includes the additional Job and Printer attributes that it supports
in Event Notification as well.


thank you,

More information about the Ipp mailing list