Until now, we have noticed only minor glitches in Feedback service running on APNS servers. These servers deliver Push messages to user's iPhone or iPod touch.
Feedback service alone is periodically checking whether target iPhone application(s) are still reachable. If the Feedback service finds out that the target Push application (special unique token used) is already uninstalled or the Push messages are not possible to deliver repeatedly for whichever reason, it automatically lists the token of that unique user as "invalid". Developer's servers have to disable that user's account temporarily to prevent unwanted resource hogging and wasted traffic on both sides. The token is marked as "valid" back again if the same user is interacting with affected Push application some time later (or new clean token is generated).
The main purpose is clear. 1) No trash 2) saved resources 3) saved processing power 4) saved traffic -- in case users are not reachable. Could be as many as hundreds of thousands.
This Feedback service is currently not responding to our servers in about 4% of cases according to our own logs. Everything else's running fine.
Feedback service alone is periodically checking whether target iPhone application(s) are still reachable. If the Feedback service finds out that the target Push application (special unique token used) is already uninstalled or the Push messages are not possible to deliver repeatedly for whichever reason, it automatically lists the token of that unique user as "invalid". Developer's servers have to disable that user's account temporarily to prevent unwanted resource hogging and wasted traffic on both sides. The token is marked as "valid" back again if the same user is interacting with affected Push application some time later (or new clean token is generated).
The main purpose is clear. 1) No trash 2) saved resources 3) saved processing power 4) saved traffic -- in case users are not reachable. Could be as many as hundreds of thousands.
This Feedback service is currently not responding to our servers in about 4% of cases according to our own logs. Everything else's running fine.
2009-06-20 17:32:08 - Feedback check...
2009-06-20 18:32:10 - Feedback check...
2009-06-20 19:32:15 - Feedback check...
2009-06-20 20:32:16 - Authentication failed because the remote party has closed the transport stream.
2009-06-20 20:32:16 - Feedback check...
2009-06-20 21:32:18 - Feedback check...