Package com.iizix.server.push.engine.transport


package com.iizix.server.push.engine.transport
  • Class
    Description
    The native Apple Push Notification service transport: held.
    The Firebase Cloud Messaging transport, HTTP v1: POST https://fcm.googleapis.com/v1/projects/{project}/messages:send with an OAuth 2.0 bearer token minted from the application's service account.
    What FcmTransport.checkToken(String, String) learnt about the Firebase project of a registration token.
    The target of a message: a registration token (message.token) or an FCM Topic (message.topic, the name without the /topics/ prefix).
    The outcome of FcmTransport.checkToken(String, String): the verdict, the application's Firebase project the token was checked against, and what FCM answered.
    A device push transport: the leg that hands a notification to a third-party store-and-forward service for one stored subscription.
    The P-256 key material of Web Push, loaded, generated and encoded with java.base only: the raw forms the wire carries - the 65-byte uncompressed point 0x04 || X || Y of a public key and the 32-byte scalar of a private key, both base64url without padding - to and from the JDK's own ECPublicKey and ECPrivateKey.
    The result of one transport send.
    Whether a transport can send for an application, and when not, why.
    The VAPID (RFC 8292) authorization for a Web Push request: an ES256 JWT over the application's key pair, presented as Authorization: vapid t=<jwt>, k=<public key>.
    The Web Push transport: RFC 8030 request, RFC 8291 encryption, RFC 8292 VAPID authorization, over the Jetty client.
    Message encryption for Web Push, RFC 8291 with the aes128gcm content coding of RFC 8188: ECDH on P-256 against the subscription's p256dh, HKDF-SHA-256 with the subscription's auth secret, one AES-128-GCM record.