On 1/20/06 3:30 AM, Alexey Proskuryakov didst favor us with:
> On 20.01.2006 10:16, "Laurence Harris" <email@hidden> wrote:
>
>> The XML times go up linearly. The binary times appear to be going up
>> exponentially. This makes the binary format completely unusable for large
>> lists with its current implementation.
>
> I think you may want to carefully consider if you want to use plist format
> at all - although it has a simple API, there are multiple disadvantages that
> may hurt you in the long run.
>
> 1) "XML" property lists are not always valid XML, so loading them with a
> compliant parser may sometimes fail, rdar://4036524. Particularly likely to
> happen if you store file names/paths there :). Not a problem if you only use
> CFPropertyList APIs, of course.
> 2) There's very little type safety in plists, e.g. unsigned 32-bit and
> signed 64-bit integers can be easily mixed up.
> 3) Their key-value pair format is pretty hard to tranform with XSLT.
>
> Even if you don't care if your data files can be opened by
> standard-compliant parsers or transformed with XSLT today, this may change
> tomorrow...
I don't think any of these would be a problem, but it does seem to be the
case that what I want to do overtaxes what property lists were designed to
do, so it looks like I'll need to find another approach to storing the data.
>
> - WBR, Alexey Proskuryakov
>
> P.S. Great research on the binary format efficiency, thank you!
You're welcome.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
