A web service protocol stack is a protocol stack (a stack of computer networking protocols) that is used to define, locate, implement, and make Web services interact with each other. A Web service protocol stack typically stacks four protocols:
- (Service) Transport Protocol: responsible for transporting messages between network applications and includes protocols such as HTTP, SMTP, FTP, as well as the more recent Blocks Extensible Exchange Protocol (BEEP).
- (XML) Messaging Protocol: responsible for encoding messages in a common XML format so that they can be understood at either end of a network connection. Currently, this area includes such protocols as XML-RPC, WS-Addressing, and SOAP.
- (Service) Description Protocol: used for describing the public interface to a specific Web service. The WSDL interface format is typically used for this purpose.
- (Service) Discovery Protocol: centralizes services into a common registry such that network Web services can publish their location and description, and makes it easy to discover what services are available on the network. Universal Description Discovery and Integration (UDDI) was intended for this purpose, but it has not been widely adopted.
The Web service protocol stack also includes a whole range of recently defined protocols: BPEL, SOAP-DSIG.
Famous quotes containing the words web, services and/or stack:
“If our web be framed with rotten handles, when our loom is well nigh done, our work is new to begin. God send the weaver true prentices again, and let them be denizens.”
—Elizabeth I (1533–1603)
“True love ennobles and dignifies the material labors of life; and homely services rendered for love’s sake have in them a poetry that is immortal.”
—Harriet Beecher Stowe (1811–1896)
““Farewell to barn and stack and tree,
Farewell to Severn shore.
Terence, look your last at me,
For I come home no more.”
—A.E. (Alfred Edward)