Mike Abdullah
Been more active on Stack Overflow this week. I reckon this would help cut down on noise: http://openradar.me/13639122
-
@mikeabdullah@benclayton In theory! -fileExistsAtPath: -isReadableFileAtPath: and co don’t have xxxAtURL: equivalent. :-(
Ben Clayton benvium
Cédric Luthi
@0xced @benclayton yes they do
-checkResourceIsReachableAndReturnError:
NSURLIsReadableKey
-
-
@mikeabdullah@0xced@benclayton I tried those a while ago and found them much slower than the path variants. -
@mjtsai@0xced@benclayton that's interesting to know. Ideally, code should avoid doing that sort of check, mind! -
@mikeabdullah@0xced@benclayton Also note that NSURLIsReadableKey and the other keys could give you a stale value due to the cache. -
@mjtsai@0xced@benclayton clear the cache first then? -
@mikeabdullah@0xced@benclayton You could, but I don’t really see the advantage compared with the path methods or stat(). -
@mjtsai@0xced@benclayton in theory (I haven't tried it) it can give your users an idea of *why* the file's not accessible. That's about it -
@mikeabdullah Anyway, I would standardize all calls to a category on NSURL. Then you can change the implementation as best practices change.
-
Michael Tsai
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.