On 17 Jun 2014, at 15:50, Sean McBride <s...@rogue-research.com> wrote:
> On Tue, 17 Jun 2014 09:17:46 +0100, Mike Abdullah said: > >> 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" > > That's a good theory. So I just looked through Foundation and found numerous > other clases that only conform to NSCoding and not NSSecureCoding like > NSAffineTransform, NSAttributedString, NSCharacterSet, etc. > > I guess I should conclude that NSSecureCoding is not a general replacement > for NSCoding and only really meant for XPC, and that Apple hasn't found much > use for sending those kinds of objects between processes. Ah, it was a nice theory, but no more than a theory then. Oh well! I think your analysis about it coming down to XPC is probably nearer the mark. _______________________________________________ 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
