On 11 Feb 2015, at 14:24, Greg Robbins <[email protected]> wrote: > Quinn, is the presence of the obscure NSURLProtocol request properties the > reason this repeatedly-requested and quite obviously needed per-task and > per-session app data support hasn't been added to NSURLSession?
First, this is really two questions, so let's break them up: o per-task -- The presence of custom protocol properties is the reason /I/ haven't asked for any extensions along those lines. o per-session -- Background sessions already support a persistent, client-controlled identifier. For in-memory sessions, I've not seen a lot of requests for such an identifier. > Are the NSURLProtocol request properties in any sense officially supported > and guaranteed to survive app and session restarts, or are they just the best > hack you've found around this negligence of the NSURLSession API design? I would consider them to be supported API. "Obscure" is not the same as "hackish". Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to [email protected]
