• 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: NSArchiver atomic?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSArchiver atomic?


  • Subject: Re: NSArchiver atomic?
  • From: Michael Vannorsdel <email@hidden>
  • Date: Sun, 29 Mar 2009 12:57:57 -0600

Guess I should clarify. Has anyone verified it; I've had an issue with partial writes archiving built-in classes. The program used to get signals to terminate and archive some basic classes (NSArray, NSString, NSNumber) to disk. But these files would only contain some of the archive about 10% of the time (just truncated), missing ending key closes ect. This has since gone away when I switched to AE (wasn't my idea to use signals) but I still wonder if it really is atomic or not.


On Mar 29, 2009, at 8:35 AM, Jim Correia wrote:

Yes - anyone who has read the API documentation for those methods knows whether or not they write the files atomically.

_______________________________________________

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: NSArchiver atomic?
      • From: Michael Ash <email@hidden>
References: 
 >NSArchiver atomic? (From: Michael Vannorsdel <email@hidden>)
 >Re: NSArchiver atomic? (From: Jim Correia <email@hidden>)

  • Prev by Date: Re: Spotlight and Leopard
  • Next by Date: Re: NSArchiver atomic?
  • Previous by thread: Re: NSArchiver atomic?
  • Next by thread: Re: NSArchiver atomic?
  • Index(es):
    • Date
    • Thread