Compatibility release

@jeffwilcox jeffwilcox released this Aug 6, 2013 · 4 commits to master since this release

This release adds a compatibility feature to support a typo/bug in the past.



@jeffwilcox jeffwilcox released this Jul 12, 2013 · 8 commits to master since this release

Moving to 2.0 to indicate the removal of old deprecated functionality.

  • createTile, createFlipTile, createToast, createRaw functions separate from send functions.
  • BREAKING CHANGE: Removes the very old liveTile, toast, rawNotification class types exposed by the module. To use this functionality for legacy apps, simply use any npm version prior to 2.0.0. The latest known version before the change was 1.2.8.
  • Increments the npm version to 2.0.0 to signal breaking change. Note that there is no major new functionality other than breaking change and an incrementally better implementation, unit tests, etc.


MPNS 1.2.8: Node 0.10.10 Fix

@jeffwilcox jeffwilcox released this Jul 2, 2013 · 16 commits to master since this release

This release contains a fix contributed by @tjunnone. Thank you!

This release is on NPM

npm install mpns


This uses the .resume() method to help make sure that connections do good things. This is a strongly recommended update for current Node build users.

From Tomas:
The message object received in the 'response' event is a stream, and must be consumed since Node.js version 0.10.x before the connection is released back to the pool. From the docs:
If you add a 'response' event handler, then you must consume the data from the response object, either by calling whenever there is a 'readable' event, or by adding a 'data' handler, or by calling the .resume() method.

This pull requests simply adds the resume method, which fixes my problem.

Associated PR: