Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I don’t get it: An URL is something that really “locates” a ressource, i.e. it holds enough information to say “man, go here, then there, and you have it!” …while an URI can say “the file is called foobar.foo … have fun finding it!”
Or am I wrong? Can the URL loading system handle URI’s? How would that look in example? For me it doesn’t make any sense that it could handle anything other than really URLs that speficy exactly where what is.
URI’s can be used to identify anything including data such as managed objects in Core Data. In that case, the URI is simply a code string that is unique to the object but doesn’t provide any other information such as what address or port the database housing the object can be contacted at.
A URI is like a Social Security number. It uniquely identifies you but doesn’t tell anyone where you live.