The Print System Asynchronous Notification Protocol is designed to be used asynchronously by clients to receive print status notifications from a server and to send back responses to those notifications. A set of notifications and responses are defined together as a notification type. The RPC interfaces and methods defined by this protocol provide a transport mechanism for arbitrary notification types.
The Print System Asynchronous Notification Protocol defines a notification type called AsyncUI. The AsyncUI notification type enables a notification source on a server to request the display of an informative alert on a client, the client to send back user input requested by the alert, and the notification source to request the execution of code that is resident on the client.
Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC 2119. Sections 1.5 and 1.9 are also normative but cannot contain those terms. All other sections and examples in this specification are informative.