IPP Mail Archive: RESEND: IPP> About notification [answers t

IPP Mail Archive: RESEND: IPP> About notification [answers t

RESEND: IPP> About notification [answers to your questions]

From: Hastings, Tom N (hastings@cp10.es.xerox.com)
Date: Mon Jun 19 2000 - 17:45:09 EDT

  • Next message: Manros, Carl-Uno B: "IPP> FW: IPP decision?"

    Vinod,

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

    Tom, Bob, and Hugo

    -----Original Message-----
    From: Vinod P N [mailto:vinodpn@teil.soft.net]
    Sent: Thursday, June 08, 2000 07:06
    To: ipp@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
                                            attribute-natural-language
                                            notification-recipient-uri

            Group2 to N:Notification attributes:
                                            notify-subscription-id
                                            printer-uri
    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).

                                            trigger-event
    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).

                                            printer-up-time
                                            job-id
                                            job-state
                                            job-state-reasons
    TH> The 3 above are only for job events.
    TH> And "job-impressions-completed" is MUST for 'job-completed' and
    'job-progress' events
                                            printer-state
                                            printer-state-reasons
                                            printer-is-accepting-jobs
    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-number RECOMMENDED
                                  printer-current-time REQUIRED if you
    support it

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

        

    thank you,
    Vinod
            



    This archive was generated by hypermail 2b29 : Mon Jun 19 2000 - 17:53:54 EDT