On Jun 4, 2016, at 14:14 , Alex Zavatone <z...@mac.com> wrote: > > Currently, the hosting app just needs 1 line of code to start up and use a > whole app that is within the framework. Not being able to get the APNS token > within our framework makes it harder to …
So why can’t the 1 line be in the app’s application:didRegisterForRemoteNotificationsWithDeviceToken: delegate method, with an extra parameter that’s the APNS token? I understand the appeal of providing a framework that’s self-contained in all its details. At the same, part of the reason we’re so deep in security doo-doo in the last 20 years is blindly trusting 3rd party components that do dangerous things without announcing the fact. In fact — and please take this as a theoretical point, since I doubt you’re interested changing course at this late date — there’s an argument that says you should handle *your* APNS notifications in a separate process (either a background app or something like an XPC process). FWIW _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
