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

Re: NSCoding


  • Subject: Re: NSCoding
  • From: Florijan Stamenkovic <email@hidden>
  • Date: Wed, 15 Oct 2008 10:38:27 -0400

Huh, I've never had data loss experiences, but then again I never really did use it for long term storage / across Java versions etc. Will need to keep this in mind though. I always assumed that as long as the internal data structure of a class does not change, the serialized data will remain readable, regardless of the functional changes in the class. Anyway, interesting, thanks.

As for NSCoder and company, never manually used it.

F

On Oct 15, 2008, at 10:22, Oliver Scheel wrote:

It depends too much on the class signature. For temporary storage it's ok, but when the class definition changes (or serialVersionUID must be modified), the data is lost. That's my experience.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >NSCoding (From: Oliver Scheel <email@hidden>)
 >Re: NSCoding (From: Oliver Scheel <email@hidden>)
 >Re: NSCoding (From: Florijan Stamenkovic <email@hidden>)
 >Re: NSCoding (From: Oliver Scheel <email@hidden>)

  • Prev by Date: Re: Using ERXEC with defaultEditingContext?
  • Next by Date: Re: You crossed editing context boundaries...
  • Previous by thread: Re: NSCoding
  • Next by thread: _rewriteURL is not called in Tomcat Deployment
  • Index(es):
    • Date
    • Thread