Redirected from XML Web Services
EDI was a precursor to web services, and is relatively difficult and expensive to implement, but reputedly reliable.
The World Wide Web Consortium has recognized that web services are an integral part of their work with XML and related technologies, and have several working groups appointed to the subject.
|
Protocols defined within the XML framework include the XML-RPC protocol for simple web services, and the SOAP and WSDL protocols for both simple and more complex web services. UDDI is for directories of services and RSS (Rich Site Summary) is an example of a very simple Web service. The composition of Web Services can be described by WSFL.
The main reason as to why Web Services are used seem to be that they rely on HTTP over TCP port 80. To understand this, keep in mind that many enterprises have protected themselves (see computer security) using firewalls, that filter and block much Internet traffic for security reasons. In this milieu, typically many ports, almost all, are closed to incoming and outgoing traffic, and the administrators of these firewalls are not eager to open them up to any traffic. However port 80 is always open, as it is used for web browsers, and thus, Web Services are appealing as they tunnel everything through port 80.
Another reason may be that prior to SOAP there were not really good interfaces to accessing functionality on different computers on a network, most of them were ad hoc and few people knew or could handle EDI, RPC and similar APIs. Web Services may have more solid frameworks and are thus easier to use.
Web services usually run on dedicated computers called application servers. There are a few brands of these:
wikipedia.org dumped 2003-03-17 with terodump