You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The message classes in the tiqr-server-libphp library used for sending push notifications were not refactored. An APNS2 message class was added that supports the new HTTP/2 based protocol. The previous APNS protocol has been deprecated and currently does not work for new apps. This issue documents some points that were noted during the implementation of the APNS2 class.
Give the message classes the same refactoring treatment as the rest of the library has had
Remove the APNS message type, this will also allow us to drop the ZF1 dependency
Android and ios PNs use different, hardcoded, timeouts (300 vs 30 seconds)
No title or subtitle is set on the push notification message
The google and apple API both support connection reuse, i.e. sending many messages over the same connection. This does not match with how the tiqr-server-libphp uses these APIs. The library opens a connection, sends the message and then closes the connection. Depending on the PN message rate the could lead to a connection rate to the PN gateway that is higher than that either google or apple are willing to accept. The only feasible way to solve this IMO would be to use a separate dedicated server process for actually sending the PNs, the tiqr-server-libphp library can than submit the PNs to this server. PHP is not a natural choice for building such a server, e.g. Java would make more sense. It has a larger choice of libraries. The tiqr-java-connector uses https://github.com/jchambers/pushy for sending APNS.
The text was updated successfully, but these errors were encountered:
This issue is imported from pivotal - Originaly created at Aug 24, 2022 by Pieter van der Meulen
The message classes in the tiqr-server-libphp library used for sending push notifications were not refactored. An APNS2 message class was added that supports the new HTTP/2 based protocol. The previous APNS protocol has been deprecated and currently does not work for new apps. This issue documents some points that were noted during the implementation of the APNS2 class.
The text was updated successfully, but these errors were encountered: