Re: NSCoding vs NSSecureCoding
Re: NSCoding vs NSSecureCoding
- Subject: Re: NSCoding vs NSSecureCoding
- From: Greg Weston <email@hidden>
- Date: Tue, 17 Jun 2014 05:30:47 -0400
Sean McBride wonders:
> 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?
Given my understanding of NSSecureCoding's implications/promises, I'm thinking NSColor and NSImage may have nothing to gain by implementing that protocol. Perhaps the (current) encoded form of those types is only a collection of scalars; object substitution isn't a meaningful concern.
_______________________________________________
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