|
| 1 | +version 0.5.0 - 2013-01-25 |
| 2 | +========================== |
| 3 | + |
| 4 | +There is lots of new stuff here but this release is backwards compatible. The |
| 5 | +REST interface operates on a different default port and runs completey in |
| 6 | +paralell with the XML-RPC one. That said, REST is the way forward and all new |
| 7 | +features will be added to that server. |
| 8 | + |
| 9 | +New: |
| 10 | + |
| 11 | + * An all-new REST interface that simplifies access to pyapns's functionality. |
| 12 | + |
| 13 | + The XML-RPC server will be depreciated over the coming years. Next year it |
| 14 | + will be "depreciated" as in it will start giving off warnings and the year |
| 15 | + after it will likely be entirely removed. |
| 16 | + |
| 17 | + * REST interface uses Apple's new "enhanced" notification format which has |
| 18 | + the ability to send back errors in the event Apple severs the connection |
| 19 | + to pyapns (which can happen for a number of reasons). |
| 20 | + |
| 21 | + * A disconnection log which will pair disconnection events with the |
| 22 | + notifications at fault. This will allow you to remove offending tokens |
| 23 | + and notifications. |
| 24 | + |
| 25 | + * The new Python client uses the very fine requests library which provides |
| 26 | + several advantages over the old XML-RPC library principally: connection |
| 27 | + keep-alive and reuse and connection pooling. |
| 28 | + |
| 29 | +Fixed Bugs: |
| 30 | + |
| 31 | + * Fixed #31/#26 - Token blacklisting - we will not blacklist tokens as it's |
| 32 | + not the job of this daemon to persist that kind of state. We however now |
| 33 | + give you the tools to blacklist tokens should you wish to do so. |
| 34 | + |
| 35 | + * Fixed #14 - Apple Dropping Connection - this can happen for any number |
| 36 | + of reasons, by using the new REST service you can get an idea of why. |
| 37 | + |
| 38 | + * Fixed #10 - reprovisioning - while this issue isn't specifically to allow |
| 39 | + reprovisioning, the reason @mikeytrw wanted the feature was to replace |
| 40 | + certs, which is now possible. |
| 41 | + |
1 | 42 | version 0.4.0 - 2012-02-14 |
2 | 43 | ========================== |
3 | 44 |
|
|
0 commit comments