Package com.iizix.server.push.engine


package com.iizix.server.push.engine
  • Class
    Description
    Finds the push configuration of an application: its .iiziPush container, which holds the VAPID key pair, the VAPID subject, the Firebase project ID and the Firebase service account.
    One resolved delivery target: a device or a live client session of one user for one application and Topic, carrying its delivery method and what that method needs.
    The in-session delivery seam: Tier 1, a write down the recipient's live IIZI session - server to AppSessionGyro to its ClientSessionGyros - entirely within IIZI transports, never VAPID or FCM.
    The push notification engine: the runtime that owns the executor, the concurrency ceiling, the store, the spool, the transports and the resolver, and performs sends.
    The collaborators of an engine, so that a test can build one without a server.
    The lightweight, immutable, in-flight notification: a title and an options map aligned to the browser showNotification(title,options) call, plus a time-to-live.
    The fluent builder of a PushMessage.
    The resolver: (application, user, Topic, [area]) -> List<DeliveryTarget>.
    Resolves an address to a location.
    Enumerates the live sessions of this server.
    A live client session of an authenticated user.
    The result of a send: the plan, the per-outcome tally and the per-target outcomes.
    One target's outcome.
    A send request: the notification, the filter, the three per-send policies (null for the server default) and the operator's authorization scope.
    The server module that runs the push engine: loaded by the server with -module com.iizix.server.push.engine.PushServerModule, initialized before the server starts, started when the server is ready and disposed with the other modules at shutdown.
    The write-ahead spool: the undelivered notifications, as a live PNSpoolerRoot tree mirrored to one XML file.
    Reads and writes the tree as XML: the server's property factory in production, a test's own in a test.
    The routing plan of a send: the resolved targets grouped into one slice per region, plus the targets the plan rejected before any dispatch and why.
    One region's slice.
    A target rejected at plan time, with its outcome.
    The subscription filter: the "group" a send targets, as a predicate over the store's dimensions plus a region selector.