[bug #16218] Problem with NSKeyedArchiver

[Michael Johnston]

Follow-up Comment #3, bug #16218 (project gnustep):

I've been investigating this further I'm pretty sure there's something wrong
with the new binary encoding. After changing all archiving operations to
explicitly use NSPropertyListXMLFormat_v1_0 and reinstalling
gnustep-startup-0.15 everything is uncoded correctly and the app behaves the
same as under 0.14. Changing any of the archiving operations to use
NSPropertyListBinaryForamt_v1_0
makes the resulting archive unreadable (except in the one case I attached in
the original submission).

I also noticed performance issues with the binary format encoding. I've
attached two logs (binaryFormat.log and xmlFormat.log) that show this by
simply bracketing an encodeObject:forKey message with NSLogs. The object
being encoded is an NSDictionary. Each object it contains is another
dictionary with 8 NSNumbers. By comparing the logs you can see that the xml
encoding is much faster (106secs to 0.5secs for 500 entries!) and linearly
dependant on the number of objects while the binary encoding seems to follow
some power dependancy.

btw Is there any way to set the encoding format globally through a default or
programmatically so you can use archiveRootObject:toFile with a format other
than the default?

Thanks

Michael
    _______________________________________________________

Additional Item Attachment:

File name: Logs.tar                       Size:10 KB
Logs comparing binary v xml encoding times.
<http://savannah.gnu.org/bugs/download.php?item_id=16218&item_file_id=3529>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=16218>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/