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.
meaning is there a difference between
<WebService(Namespace:='http://theurl.com/')> and
<WebService(Namespace:='http://www.theurl.com/')> ?
Don’t know if you’re asking one of two things so I’ll mention both.
1. What’s the namespace for?
The reasons all derive from the W3C standards.
Very short answer: If you’re doing some simple ASP.NET web services, all connecting through .NET you’ll probably never know any difference. In fact, a lot of web services I’ve seen I see are still using tempuri.org 😉 Shame. If you’re doing interop or are publishing a number of web services, a proper namespace guarantees uniqueness for similarly named services.
2. Does the subdomain matter?
Yes, different subdomain, therefore, while semantically equivalent, they’re different namespaces. A namespace can look like a Url, but it’s not. You could just as easily use something like "urn:org.tempuri" as a valid namespace.