Skip to content

Commit 1cef069

Browse files
committed
clarity TNPG instructions
1 parent e52a868 commit 1cef069

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

server/push/tnpg/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# TNPG: Push Gateway
22

3-
This is push notifications adapter which communicates with Tinode Push Gateway (TNPG).
3+
This is a push notifications adapter which communicates with Tinode Push Gateway (TNPG).
44

55
TNPG is a proprietary service intended to simplify deployment of on-premise installations.
66
Deploying a Tinode server without TNPG requires [configuring Google FCM](../fcm/) with your own credentials, recompiling Android and iOS clients, releasing them to PlayStore and AppStore under your own accounts. It's usually time consuming and relatively complex.
77

8-
TNPG solves this problem by allowing you to send push notifications on behalf of Tinode: you hand a notification over to Tinode, Tinode sends it to client using its own credentials and certificates. Internally it uses [Google FCM](https://firebase.google.com/docs/cloud-messaging/) and as such supports the same platforms as FCM. The main advantage of using TNPG over FCM is simplicity of configuration: mobile clients don't have to be recompiled, all is needed is a configuration update on the server.
8+
TNPG solves this problem by letting Tinode LLC (the company behind Tinode) to send push notifications on your behalf: you hand a notification over to TNPG, TNPG sends it to the clients using its own credentials and certificates. Internally it uses [Google FCM](https://firebase.google.com/docs/cloud-messaging/) and as such supports the same platforms as FCM. The main advantage of using TNPG over FCM is simplicity of configuration: you can use stock mobile clients with your custom Tinode server, all is needed is a configuration update on the server.
99

1010
## Configuring TNPG adapter
1111

0 commit comments

Comments
 (0)