Why not use path-based API? (was: Loading image resources)
Why not use path-based API? (was: Loading image resources)
- Subject: Why not use path-based API? (was: Loading image resources)
- From: Aandi Inston <email@hidden>
- Date: Sun, 14 Sep 2014 08:57:52 +0100
> No one should be using path-based API any more, generally.
> You should use URL-based equivalents.
Why? Really, why? Certainly there are APIs where we have to use URL's and
we have to convert the path into a URL, but where a non-deprecated
path-based URL exists, what current or future obstacles do you foresee? The
URL doesn't seem to be more predicable or persistent, for example.
Thanks for any insight. I've been really happy to see the last of the
old-style colon-separated names and move to something I can understand, a
pathname.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden