Анализ страницы https://unifiedpush.org/developers/spec/dbus/

D-Bus | UnifiedPush

UnifiedPush Spec: DBUS_0.3.0 Index Resources Connector API org.unifiedpush.Connector2.Message org.unifiedpush.Connector2.NewEndpoint org.unifiedpush.Connector2.Unregistered Distributor API org.unifiedpush.Distributor2.Register org.unifiedpush.Distributor2.Unregister Appendix: Implementation practices Registration D-Bus Service Choosing a distributor On Application Startup D-Bus Interface Introspection XML files References Internal References Normative References Informative References Resources All String argument MUST be UTF-8 encoded. Any call containing a parameter field that do not follow the specification MUST be ignored. For example, a call with “not_an_url” for the “endpoint” must be ignored. End user application: This is the application that will receive notifications with UnifiedPush; All the logic required for the end user application can be done with a library. Connection Token: This is a randomly generated token to identify the registration from the connector and the distributor. This token is generated by the connector, and send for the first time during the registration intent (org.unifiedpush.Distributor2.Register). This token must contain sufficient entropy so it cannot be guessed. To generate this token, UUIDv4 (RFC9562) is suggested. It is unique on distributor and connector side. Every requests to the connector contains this token. If the connector doesn’t know this token, the request is ignored. This is a string of maximum 100 bytes. VAPID public key: This is a public key on the P-256 curve encoded in the uncompressed form SEC 1 (section 2.3.3, replicated from X9.62), and base64url encoded RFC7515. This public key is generated by the end user application, and send during the registration intent (org.unifiedpush.Distributor2.Register). It is used by the application server to identify itself to the push server, following the RFC8292. Some distributors MAY require a valid VAPID key, and response with a registration fail if not present ([org.unifiedpush.android.connector.REGISTRATION_FAILED]). This is a 87 bytes long string. Push message: This is an array of bytes (Array<Byte>) sent by the application server to the push server. The distributor sends this message to the end user application. It MUST be the raw POST data received by the push server (or the rewrite proxy if present). The message MUST be an encrypted content that follows RFC8291. Its size is between 1 and 4096 bytes (inclusive). Endpoint: This is the URL of the push resource as defined by RFC8030. This url point to the push server and is distributed to the end user application by the distributor. This MUST be at most 1000 bytes. As defined by RFC8030, authorization is managed using capability URLs (CAP-URI). Therefore, the endpoint MUST contain enough random entropy to ensure it is diffucult to successfully guess a valid URL. We recommend using a 160 bits (20 bytes) random value URL-safe base64 encoded string. Short description of the registration: This is a string send by the end user application during registration describing the registration purpose (eg. the account name of the application) the distributor may show on its user interface. It is at most 100 bytes long string. Connector API The connector MUST provide a service with a name identifying the application (standard reverse DNS style application ID, which is also used in D-Bus APIs). This value is passed to the distributor during the registration when org.unifiedpush.Distributor2.Register is called.

https://unifiedpush.org/developers/spec/dbus/

Ошибок нет

width=device-width, initial-scale=1.0

Кол-во: 5

Кол-во: 15