Skip navigation.
 
mlRe: Archiving's Future?
FROM : Ali Ozer
DATE : Sun May 01 18:16:22 2005

Several optimizations were made in Tiger; if you're still seeing 
issues in your usage, please submit bugs (or refresh previously 
submitted bugs...). However note that as with archiving, keyed 
archiving is currently a write all/read all solution, meaning it's 
not appropriate for very large files. Switching from XML format keyed 
archives to binary format keyed archives provides significant 
improvement, but it's still not an incremental format at this point. 
Hence what I meant by "this context."

CoreData with SQL files is much more appropriate for potentially 
large files that need to be read/written incrementally.

Ali



Begin forwarded message:
> From: Georg Tuparev <<email_removed>>
> Date: May 1, 2005 2:05:17 PDT
> To: Ali Ozer <<email_removed>>
> Cc: Cocoa List <<email_removed>>
> Subject: Re: Archiving's Future?
>
>
> In this context, when will be keyed archive reasonably fast?
>
> gt
>
> On May 1, 2005, at 6:05 AM, Ali Ozer wrote:
>
>

>> In this context, keyed archiving.
>> Ali
>>
>>
>>
>> Begin forwarded message:
>>
>>

>>> From: Greg <<email_removed>>
>>> Date: April 30, 2005 20:19:55 PDT
>>> To: <email_removed>
>>> Subject: Archiving's Future?
>>>
>>> I just read through the foundation release notes and saw at the 
>>> bottom about API deprecations:
>>>
>>> "The NSArchiver and NSUnarchiver classes and other APIs in 
>>> NSArchiver.h are not deprecated in this release, but may be in 
>>> the next release."
>>>
>>> I would just like to know, what the migration path is recommended 
>>> by apple? keyed archiving? core data?
>>>
>>> Greg
>>>
>>>

> Georg Tuparev
> Tuparev Technologies
> Klipper 13
> 1186 VR Amstelveen
> The Netherlands
> Mobile: +31-6-55798196
>
>

Related mailsAuthorDate
mlArchiving's Future? Greg May 1, 05:19
mlRe: Archiving's Future? Ali Ozer May 1, 06:05
mlRe: Archiving's Future? Georg Tuparev May 1, 11:05
mlRe: Archiving's Future? Ali Ozer May 1, 18:16