Problem with NSURL/CFURL, and/or web servers?
Problem with NSURL/CFURL, and/or web servers?
- Subject: Problem with NSURL/CFURL, and/or web servers?
- From: Angela Brett <email@hidden>
- Date: Sat, 27 Apr 2002 00:53:27 +1200
Hello,
I've noticed in the past that sometimes when Omniweb is downloading a
file, it will stop in the middle (even though it knows how much of
the file is left to go) and act like it's downloaded the whole thing
when it hasn't. It seems to happen more for particular files, or
particular servers. Sometimes I can download a whole file, sometimes
just part of it. I thought that was something wrong with Omniweb,
since I'd never had that happen in other (pre-OSX) browsers and I
haven't used any other OS X browsers extensively.
Now, just after the website my app downloads files from has been
relaunched/reorganised (I don't know if it's on a different server or
not) my app has been having the same problem. I'm using NSURL's
loadResourceDataNotifyingClient:usingCache: and using
resourceDataUsingCache:YES to get the data and save it, in my
URLResourceDidFinishLoading: method. Now, sometimes it saves the
files when they're incomplete. I tried loading one of the URLs in
Omniweb to make sure there was nothing wrong with the files
themselves. Omniweb also stopped part-way through loading it,
although it loaded more of the file than my app had. The same thing
happened in Netscape for OS X, but Classic versions of both Netscape
and IE loaded the whole thing first time.
The server is kind of slow, but I don't think this is a timeout issue
since Omniweb was happily waiting for something else to load in
another window before, during and after partially downloading the
file.
So, does anyone know what causes this? It certainly seems to have
something to do with the server, from my experience with downloading
in Omniweb and my own app. And yet, NSURL must play a part, since
Classic web browsers had no problems. I don't know much about Carbon
but I suppose Netscape for OS X uses CFURLs, which I think are
basically the same thing. Perhaps the server is sending some kind of
signal (or lack of signal) which NSURL interprets as signifying the
end of the file when it doesn't. Also, is there any way to prevent
the premature end of downloads? I guess not, since if there were a
way, the people at Omni would have found it... but I can always hope.
--
Angela Brett email@hidden
http://acronyms.co.nz/angela
A mathematician is a machine for turning coffee into theorems -- Paul Erdos
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.