Thursday, May 14, 2009

How to Use: Web Applications Services

A Web application Service is defined by the W3C as a software system designed to support Machine to Machine (M2M) interaction over a Internet i.e. Network. Web services are just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services also.

The W3C Web service definition encompasses many different systems, but in common usage the term refers to client and server that communicate using some types of messages that follow the SOAP standard. Common in both the field and the terminology is the assumption that there is also a machine readable description of the operations supported by the server written in the WSDL(Web Services Description Language).

The latter is not a requirement of a SOAP endpoint, but it is a prerequisite for automated client-side code generation in many Java and .Net OAP frameworks (frameworks such as Spring and Apache CFX being notable exceptions). Some industry organizations, such as the WS-I mandate both SOAP and WSDL in their definition of a Web service.

A new outline of web site design proceeds to use of web applications services more and more. The target of this article is to show some possibilities of their usage. Usually, services providing content for web pages are included into their code. The integration of other sources is possible in a few different ways:

No comments:

Post a Comment