Release Note 1.5.1

7-Nov-2013

This release contains some minor bug fix and improvements.

ChangeLog:

• bugfix Correctly change from sandbox to production environment in APNS. This fixed issue 33.
• bugfix If a connection pool connecting with APNS closed, then any Close() operation on connections from the pool will cause a panic. This is a bug in connpool, and fixed in issue 37.
• improvement APNS: add content-available support. Fixed issue 36.
• improvement Set Keepalive for all TCP connections. In this case, we can discover connection failure quickly. Fixed issue 38.
• improvement @ is a valid character in subscriber and service names. Fixed issue 39.

Release Note 1.5.0

1-Sep-2013

We support ADM for Kindle tablets in this version.

ChangeLog:

• improvement Add ADM support. Fixed #29

Release Note 1.4.5

1-Aug-2013

This version contains only one bug fix. Thanks for cmabastar-gumi's bug
report.

ChangeLog:

• bugfix Fixed a nil pointer error described in #28.

Release Note 1.4.4

19-Jul-2013

This version contains some minor bug fixes and a huge improvement for APNS. I
would like to give special thanks to cmabastar-gumi for his detailed bug
reports.

ChangeLog:

• bugfix Removed some unnecessary information in the
  notification when call on /push. In old versions, service
  and subscriber(s) names will be included in the notification.
  This may leak some information to the client (e.g. how you name
  the client internally.) Fixed issue 19.
• bugfix Fixed a potential memory leak bug affected APNS sandbox
  environment. Fixed issue 25.
• bugfix For APNS, uniqush-push now checks the payload size before sending it. Fixed issue 24.
• improvement For APNS, uniqush-push now checks the feedback service less frequently so that the performance can be improved a lot. Fixed issue 26.
• improvement Added a connection pool support for APNS. Partially fixed issue 27.
• improvement For APNS, uniqush-push now does not wait for the error
  response. This is a trade-off to improve the performance. However, for most
  errors, uniqush-push is able to check them before sending the notification to
  APNS. For others, uniqush-push is able to recover the error. More details
  will be discussed on the blog. Partially fixed issue 27.

Release Note 1.4.3

14-May-2013

This version contains some minor bug fixes and added some hidden feature making it works with uniqush-conn.

ChangeLog:

• bugfix Close response body on HTTP response in GCM and C2DM code. This is a
  very common error when using Go's http client package. I
  thought I have fixed this someday in the past, but it turns out I was wrong.
  Anyway, this fixed issue 13.
• bugfix Fixed a bug introduced by feedback support in APNS. It is a
  missing-return-statement error. Fixed by
  infiniteloop5 through pull request #17
• bugfix Fixed some error in document. Fixed issue 16 reported by user974256.
• improvement We do not depends on redis now. Well, not exactly. You just don't need to install redis on the same machine with uniqush-push. Fixed issue 18.
• feature Added a new URL path: /nrdp. Users can check how many delivery points are there under certain subscriber. This feature will be used by uniqush-conn and is considered as a hidden feature. i.e. not intended to be used by users. Fixed issue 14.
• feature Added the so-called _perdp._* feature. This feature is also used by uniqush-conn and is a hidden feature as well. Fixed issue 15.

Release Note 1.4.2

1-Apr-2013 ( This is not a joke! )

This version contains several bug fixes and a refactory of the main package.

ChangeLog:

• bugfix Stop on /stop. Sorry, I forgot to implement the feature after refactoring the main package. Fixed issue 9.
• bugfix Stop on SIGTERM. Similar with issue 9. User can now stop the program by sending SIGTERM to the process. Fixed issue 8.
• bugfix Fixed a nil-pointer crash bug. The program will experience a nil-pointer crash (samething as NULL pointer) under some conditions. For example, if user provides an invalid APIKEY for a GCM provider, then uniqush-push will crash when the user tries to push through this malformed provider. Fixed issue 10.
• feature Support Feedback Service in APNS. Fixed issue 3.

Release Note 1.4.1

24-Feb-2013

This version contains several bug fixes and a refactory of the main package.

ChangeLog:

• improvement On (un)subscription, the log message now contains service and subscriber information. Fixed issue 2.
• improvement On adding an APNS push service provider, uniqush-push will report error immediately if the given certificate or key files do not exist. Fixed issue 6.
• bugfix Removed all code related memory pool. There is no dependency on memory pool any more. Fixed issue 7.
• improvement Rewrote the code in main package. It is more clean, simple and less redundant. Fixed issue 5.

Release Note 1.4.0

7-Jan-2013

This version contains several bug fixes, new features and interface changes for developers.

ChangeLog:

• bugfix Fixed the bug on re-connecting APNS server. Thanks to Ivan Yu for his detailed bug report and analysis
• feature Added loc-key, loc-args and action-loc-key support for APNS. You can send your localized message through uniqush-pus now. This part of code is adapted from benwei's patch. Thank you, benwei. Here is an example of using loc-key and loc-args: curl http://127.0.0.1:9898/push -d service=fake -d subscriber=client -d msg="hello" -d loc-key="lockey" -d loc-args="hello,world" Then the loc-args sent to the APNS will be ["hello", "world"]. Yes. it is comma separated. If one of your loc-key contains comma(,), then add a backslash () in front of the comma. (Similar to escape character in C)
• feature Added support to true multicast for GCM.
• feature Added time-to-live support for both GCM and APNS. It defines how long (in seconds) the message should be kept on push service provider's server if the device is offline.
• change When subscribe to a GCM service, the user don't need to provide the account parameter. When unsubscribe a service, the user need to provide the same regid as the one he used to subscribe. For existing subscribers (i.e. the subscriber is added using previous releases), the account parameter is required when unsubscribe the service.
• change This change only affects developers. The interface of PushServiceType is changed making it possible to support true multicast on GCM. Corresponding components are changed.

Release 1.3.2 (legacy)

Legacy release for uniqush-push 1.3.2. This contains packages previously hosted on uniqush.org (the packages were moved to GitHub releases)

You probably want the latest releases: uniqush-push 2.5.0 or newer

This is a bug fix version. No new features were added.

• bugfix Fixed a bug on unsubscription. When a user unsubscribed from a
  service and subscribe it again, the database will be in an error state.
  Reason: uniqush-push keeps a counter for each delivery points. When a user
  unsubscribes, its related delivery point's counter will be decreased by one.
  When the counter reaches zero, its corresponding delivery point information
  will be deleted. However, in old versions, uniqush-push will not delete the
  counter when it reaches zero. Hence there is a bug. This bug was found and
  reported by Ivan Yu.
• bugfix Fixed a bug when subscribe with identical information. If a delivery
  point subscribe a service, its corresponding counter will be increased by
  one. If the delivery point has already been added under a certain user, its
  counter should not be increased. However, in old versions, uniqush-push will
  increase the counter without checking if the delivery point has already under
  the same user. This bug was found and reported by Ivan Yu.
• The uniqush organization on github moved three
  repositories under [uniqush-push repository] to merge them into a single
  repository. Old repositories will be removed soon. They are: pushdb, which
  now under db directory in [uniqush-push repository]; pushsys, which now
  under push directory in [uniqush-push repository]; pushsrv, which now under
  srv directory in [uniqush-push repository].

Special thanks to Ivan Yu for his bug report.

Release 1.3.1 (legacy)

Legacy release for uniqush-push 1.3.1. This contains packages previously hosted on uniqush.org (the packages were moved to GitHub releases)

You probably want the latest releases: uniqush-push 2.5.0 or newer

• This version introduced wildcard feature, which allows users use a wildcard to send notification to multiple subscribers.

• For more details, read this blog post.