Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / September 2006

Tip: Looking for answers? Try searching our database.

WSDL = SOAP?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jon Davis - 06 Sep 2006 23:14 GMT
When people discuss XML Web Services in the context of .NET, and they talk
about their WSDL file and the like, does this infer SOAP? Or are there other
XML-based web protocols besides SOAP that depend on WSDL files?

WSDL aside, on the .NET platform, when people discuss XML Web Services, is
SOAP typically inferred?

Just asking about everyday industry conversation here. I seem to be on
another page with some people, as I assume SOAP (and not REST or XML-RPC or
anything else) when people put .NET and XML web services in the same
sentence and don't mention their protocol.

Jon
John Saunders - 06 Sep 2006 23:21 GMT
> When people discuss XML Web Services in the context of .NET, and they talk
> about their WSDL file and the like, does this infer SOAP? Or are there
[quoted text clipped - 7 lines]
> or anything else) when people put .NET and XML web services in the same
> sentence and don't mention their protocol.

Most XML web services use SOAP, but this is not required. The WSDL file can
specify more than one transport, more than one encoding, etc.  One could use
encrypted and compressed binary over SMTP if needed, and you'd still specify
it with a WSDL document.

I don't know of any reason to use XML-RPC in new development. It was a
starting point for SOAP, but SOAP has left it far behind.

John
Jon Davis - 07 Sep 2006 00:07 GMT
> Most XML web services use SOAP, but this is not required. The WSDL file
> can specify more than one transport, more than one encoding, etc.  One
> could use encrypted and compressed binary over SMTP if needed, and you'd
> still specify it with a WSDL document.

SMTP? But then what is the 'W' in WSDL?

I'm familiar with WSDL enough to have my own opinion but would you say that
WSDL is, in function / purpose, akin to a DTD / schema but specifically for
transport / deserialization?

Jon

>> When people discuss XML Web Services in the context of .NET, and they
>> talk about their WSDL file and the like, does this infer SOAP? Or are
[quoted text clipped - 18 lines]
>
> John
Gaurav Vaish (www.EduJiniOnline.com) - 07 Sep 2006 00:58 GMT
> SMTP? But then what is the 'W' in WSDL?

   Still Web.
   Well... 'W' cannot be read without 'S'.
   So, 'WS'-'D'-'L'... A description language describing a WebService.

   If one looks at the bindings section of WSDL, it would be clear that:

1. WSDL can have a SOAP binding.
   Other bindings are also possible
2. The WebService location can be an HTTP URL
   For SMTP, the location may be an email address.

> I'm familiar with WSDL enough to have my own opinion but would you say
> that WSDL is, in function / purpose, akin to a DTD / schema but
> specifically for transport / deserialization?

   Kind of... yes.
   Specifying what is the content to be sent and received on the wire and
to/from what location.

Signature

Happy Hacking,
Gaurav Vaish | http://www.mastergaurav.com
http://articles.edujinionline.com/webservices
-------------------

John Saunders - 07 Sep 2006 02:12 GMT
>> Most XML web services use SOAP, but this is not required. The WSDL file
>> can specify more than one transport, more than one encoding, etc.  One
>> could use encrypted and compressed binary over SMTP if needed, and you'd
>> still specify it with a WSDL document.
>
> SMTP? But then what is the 'W' in WSDL?

W == "Web", so what? Were you serious?

> I'm familiar with WSDL enough to have my own opinion but would you say
> that WSDL is, in function / purpose, akin to a DTD / schema but
> specifically for transport / deserialization?

No. It describes one or more web services;  it describes the messages they
use to communicate, including the schema(s) which describe the messages; it
describes the operations of the web service, and groups of those operations;
and it describes the bindings between the groups of operations and a
particular transport.

This is not quite a schema for web services, in my opinion. It's more
dynamic than a schema or DTD.

John

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.