Package com.iizix.push
package com.iizix.push
- ClassDescriptionWhich delivery tiers a send is permitted to use.The per-target outcome of a push send, recorded for every subscription the send's filter matched.How hard the engine works to deliver a notification quickly.The Push Notification (PN) API of one application session: the fan-out sends, and the calls that need a particular client, which take that client and delegate to its
IPushNotificationAPI.What one device can do for Push Notification right now, as the client reports it.An immutable Push Notification — the smallest piece, the payload that travels unchanged from caller to recipient.The Push Notification (PN) API of one client session: the device the user is on right now.The members shared by the two server-side Push Notification (PN) APIs: the client session'sIPushNotificationAPIand the application session'sIAppSessionPushNotificationAPI.The Push Notification (PN) engine — the runtime that owns the executor, the concurrency ceiling, the spool, the transports, and the region router, and that performs sends.Observer of the Push Notification (PN) events of one session's user and application, registered withIPushNotificationCommonAPI.addPushNotificationListener(IPushNotificationListener)and held in acom.iizix.GenericListener.A fluent builder for constructing aIPushNotification.The Push Notification (PN) service facet of the server.Receives progress notifications as a bulk send's region slices complete.A client's report about one notification it was sent: that it was shown, or that the user clicked it.A complete request to send a notification: what to send, to whom, and under which policies and authority.The result of a send made through the Push Notification API, with the outcome of every target.Configuration contract for the Push Notification service.The result of a successful subscribe: whether a subscription was newly stored, and the subscription as it now stands.One stored subscription, as a listing shows it: whose, for what, on which device, through which transport, and when.The outcome of a send for one target: one device subscription, or one live client session reached in-session.The Java registration of Push Notification HTTP API users (ruling R6): program users held in memory beside the users of the credentials file (PUSH-CREDENTIALS section 7).A subscription filter — the "group" a send or admin operation targets.Thrown when a send's operator is not authorized for a region the send's plan requires.The lifecycle state of theIPushNotificationEngine.The Push Notification (PN) key files ofPUSH-KEYFILES-DESIGN.md: the key directory (section 2), the references written in.iiziPushand in the credentials file's[server]section (3.2), and the one reader that turns a reference into key material (section 5) - for the server and the Designer alike.A key file that cannot be used: the file and the reason, never a byte of the file.A Firebase service-account key file as read.A VAPID key file as read: the pair it holds, validated and belonging together.Loads a VAPID key file as its$pushcontainer: the server's property factory in production, the Designer's property manager, a test's own.Watches a key file for the owner of the watcher: the engine'sPushFileWatcheron a server.The seam through which the Push Notification (PN) engine implementation reachescom.iizix.core.The failure a Push Notification (PN) API callback receives when an operation is refused or cannot be carried out, carrying a reason code a program can branch on.The notification permission of a device, as the device itself reports it.The aggregate result of a send — the audit record and theServerAdminUI's data source in one object.The per-send options of the Push Notification API.The device push transports, i.e.The strictness with which a send honours data-residency constraints when a subscription's region cannot be resolved.Helper class to generate VAPID keys for use with Push Notification.