Re: Persistance
Re: Persistance
- Subject: Re: Persistance
- From: Chris Kane <email@hidden>
- Date: Tue, 9 Oct 2001 17:43:33 -0700
At 10:59 AM +0200 10/9/01, Marcel Weiher wrote:
Objective-XML, for example, has an NSArchiver implementation that
generates XML files using NSCoding protocol. I am currently looking at
making the generated XML SOAP compatible (as much as feasible).
Apple also has a named-value encoder/decoder that generates XML, waiting
in the wings. We hope to introduce it in the next OS release. The
bigger project is converting AppKit and Foundation to take advantage of
it (to achieve the backwards AND forwards compatibility).
But I don't want to rain on anybody's project in mentioning this. By
writing your own coder, one can do it the way you want to, have the
features you want it to have (which Cocoa's may not), and potentially
leave out things you don't need, which may make it faster, or produce
smaller output, or in some other way better than Cocoa's. For some, for
example, using a technique like NSKeyValueCoding to do limited
"automatic" archiving has appeal (I pick that as one example, since it's
a suggestion that comes up every so often). Or, as another example,
your own coder may not have to be compatible with the current archiving
mechanism.
I would be interested in hearing from anyone who's written their own
coder that would like to share their solution to the 'half-initialized
object' problems during decoding, if they've solved them.
Chris Kane
Cocoa Frameworks, Apple
PS: no, I won't talk about any of the details or delivery specifics.