• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSCoding vs NSSecureCoding
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSCoding vs NSSecureCoding


  • Subject: Re: NSCoding vs NSSecureCoding
  • From: Mike Abdullah <email@hidden>
  • Date: Tue, 17 Jun 2014 09:17:46 +0100

On 17 Jun 2014, at 00:33, Sean McBride <email@hidden> wrote:

> Hi all,
>
> I was modernizing some of my code to support NSSecureCoding instead of just NSCoding and stumbled upon that fact that NSColor and NSImage support only NSCoding and not NSSecureCoding.  Whereas NSURL, NSData, NSArray and countless others now support NSSecureCoding.
>
> Is it just that Apple hasn't gotten around to NSColor and NSImage, or is there some rationale I'm not seeing?

I suspect the rationale might be “NSColor and NSImage live in AppKit, not Foundation, and the AppKit engineers aren’t so bothered about secure coding"


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


  • Follow-Ups:
    • Re: NSCoding vs NSSecureCoding
      • From: Sean McBride <email@hidden>
References: 
 >NSCoding vs NSSecureCoding (From: Sean McBride <email@hidden>)

  • Prev by Date: app icon for Launchpad
  • Next by Date: Re: NSCoding vs NSSecureCoding
  • Previous by thread: NSCoding vs NSSecureCoding
  • Next by thread: Re: NSCoding vs NSSecureCoding
  • Index(es):
    • Date
    • Thread