I would assume the response is received by the hardware and possibly cached until it can be consumed by the application. The problem, IMHO, would be that the application may not resume, so either iOS will dump the message or it will be delivered but there might no longer be a listener for it to be received by.
Either way, the upshot would be that either it’s received after a delay (coming back to your app) or it fails completely but your app won’t know that it failed anyway. This would be one advantage of asynchronous network calls, I suppose.
Have you actually tried it? [import]uid: 8271 topic_id: 27355 reply_id: 111124[/import]