(2) the Subscription object is deleted, when the Per-Printer Subscription lease time expires, or (3) the 'job-completed' event occurs for a Per-Job Subscription. This condition also occurs for a Get-Notifications request that a Notification Recipient makes after the job completes, but before the Event Life expires.
11. Encoding and Transport
This section defines the encoding and transport considerations for this Delivery Method based on [RFC2910].
The encoding of a Get-Notifications Response is modeled after the Get-Jobs Response (see [RFC2911]). In a Get-Notifications Response, each Event Notification Attributes Group MUST start with an 'event- notification-attributes-tag' (see the section "Encodings of Additional Attribute Tags" in [RFC3995]), and end with an 'end-of- attributes-tag'. In addition, for Event Wait Mode the multi- part/related is used to separate each multiple response (in time) to a single Get-Notifications Request.
The Printer returns Get-Notification Response as follows:
1. If the Notification Recipient client did not request Event Wait Mode ("notify-wait" = 'false' or omitted), the Printer ends the response with an 'end-of-attributes-tag' (see [RFC2911], Get-Jobs encoding), as with any operation response.
2. If the Notification Recipient client requests Event Wait Mode ("notify-wait" = 'true') and the Printer wishes to honor the request, the Printer MUST return the response as an application/ipp part inside a multi-part/related MIME media type. When one or more additional Events occur, the Printer returns each as an additional Event Notification Group using a separate application/ipp part under the multi-part/related type.
3. If the client requested Event Wait Mode ("notify-wait" = 'true'), but the Printer does not wish to honor the request in the initial
精品推荐