Releases: jchambers/pushy
Releases · jchambers/pushy
v0.2 - Bug fixes and shutdown behavior improvements
This release of Pushy improves shutdown behavior and fixes a number of bugs.
New features and improvements
- Shut down connections by sending a known-bad notification; this significantly increases our confidence about which notifications have been processed by the APNs gateway and which haven't (#4)
- Significantly reduced the number of threads used by Pushy (#9, #13)
- Simplified rejected notification handling
- Made logging generally more robust
Bug fixes
- Fixed an issue where any exception could cause client threads to terminate unexpectedly (#5)
- Fixed a race condition where rejection notifications from the APNs gateway could be lost (#6)
- Fixed an issue where shutting down immediately after starting could throw a
NullPointerException
(#8) - Added a read timeout to the feedback client, which resolves an issue where the APNs feedback service is never actually guaranteed to close the connection (#15)
- Fixed a rare
NullPointerException
that could sometimes occur if a connection attempt succeeded, but a TLS handshake failed (#27) - Fixed a bug where rejected notification listeners could be incorrectly removed from the listener pool
v0.1.1 - Now with more Maven
While there are no functional changes in this update, we've made some infrastructural upgrades:
- Project is now available via the Maven central repository
- Updated to Netty 4.0.7
- Dropped slf4j-simple as a dependency (it should be up to Pushy users which slf4j implementation they want to use)
v0.1 - Initial public release
Initial public release of Pushy.