Re: NSPersistentDocument, Core Data & Cryptation
Re: NSPersistentDocument, Core Data & Cryptation
- Subject: Re: NSPersistentDocument, Core Data & Cryptation
- From: Nicko van Someren <email@hidden>
- Date: Sun, 19 Jun 2005 15:13:53 +0100
On 17 Jun 2005, at 19:58, mmalcolm crawford wrote:
On Jun 17, 2005, at 5:14 AM, Nicko van Someren wrote:
*** Uncaught exception: <NSInvalidArgumentException> CoreData
only supports file URLs.
While I can see why it would be necessary to impose such a
limitation on SQLite stores it seems a rather unnecessary
restriction on stores which load the whole file at once. Come on
Apple; we live in a web connected world so why can't we read our
data files over HTTP, FTP or something else we've not thought of yet?
This is a general issue with Cocoa. Please file an enhancement
request.
I'll do that.
Note, though, that in general there's probably little reason why
data could not be read -- the problem is more likely to be with
*writing*...
<Grumble>
That's only because Apple's support for sending stuff through URL
protocols is so crummy! I filed bug reports on this ages ago but it
seems to me exceptionally bad form that all the
initWithContentsOfURL: methods in foundation classes work with any
sort of URL but the corresponding writeToURL:... calls don't. HTTP
and FTP "put" operations are really no harder to implement at the
client than "get" operations.
</grumble>
Irrespective of the state of the "put" capability with the standard
URL protocols, in the presence of a structured URL protocol handling
architecture and an API which requires the user to provide the
location of the data in URL form is seems sloppy for the data not to
be fetched through the architecture that is already there.
Nicko
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden