-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standard between Push Server and Push Distributor #38
Comments
The way push notifications are sent from the push server to the push distrib is out of scope. We already have different protocols |
No we don't have. Of course, we have communication protocols for everything, but no standard that says one of them and specific way using it in the case of push notifications. That's why ntfy and nextpush are not compatible, you can't use nextpush Push Disttributor with ntfy-server Push Server. I agree that the standard is hardly worth including in UnifiedPush, but then we could make separate standard for it. As we have SMTP and IMAP. |
That's the idea of the protocol. You can use different servers and client. If a new protocol arrives with very good performances then it is possible to do a new distributor which will be automatically compatible with apps supporting UnifiedPush ATM, ntfy uses WebSockets or HTTP JSON stream, NextPush SSE, Conversations XMPP and UP-FCM Distributor FCM |
True and that's why I suggest separate protocol for this. In the long run, standardizing it would also be beneficial, right? |
Can we expand this or make separate standard between Push Server and Push Distributor?
The text was updated successfully, but these errors were encountered: