3.1.1.6 Other Local Events

This protocol does not define the set of printing events that cause notification sources to trigger notifications.

When a notification source opens a Bidirectional Notification Channel (section 3.1.1.1) or sends a unidirectional notification, it MUST associate a PrintAsyncNotificationType value (section 2.2.1) with the request. That value SHOULD be used to match the request to a Client Registration (section 3.1.1.1). The notification source MUST also associate a PrintAsyncNotifyUserFilter value (section 2.2.2) with the request, to facilitate the application of a user identity filter in performing such matches. If the PrintAsyncNotifyUserFilter value is kPerUser, the notification source MUST also associate with the request the authenticated user identity of the user who is the intended target for receiving the notifications. The rules for interpreting PrintAsyncNotifyUserFilter values to apply a user identity filter are specified in section 2.2.2.