A Web application Service is defined by the W3C as a software system designed to support Machine to Machine (M2M) interaction over a Internet ie 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 encompasss many different systems, but in common use the term refer to client and server that communicates using the types of messages that follow the SOAP standard. Common in both the field and the terminology is the addition 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 noticable 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 proceeded 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:
o by i-Frame (Inline frame)
o By Using Framesets
o by Using Ajax
o and using server technologies
Web applications integration
The integration by using the inline frame i-frame technology is quite easy and does not require much special knowledge. A webmaster (or an editor) only needs to know where to include the content, the expected size and the URL.
Framesets should be used only when it is not possible to do it the other way. Frames are necessary in some of the Internet applications, because they lower data flows' volume. A good example of such an application is an internet chat. In spite of that, there are AJAX techniques, which are able to avoid the use of framesets.
This technology has one security-based restriction against iframe or framesets. That is an unavailability of pages (data) not located at the same web server (or even in the same URL path).
Restriction of AJAX still can be suppressed by the use of server-side techniques. Server programming languages can read remote web pages too.
In combination of server-side and client-side methods, there is a chance for building interactive web sites rich in user supporting elements.
With a server programming interaction, several web application services have been prepared. We would like to present some of our own solutions.
Examples of services for web sites:
oa short message service support
oa meteorological forecast
o calendar services
o rss feeds
The RSS service has four different versions up to now. These are versions 0.9, 0.9x, 1.0 and 2.0. Every version has its own specifics, but all of them are based on XML. The 1.0 version is applied using RDF. The simplest versions for developers are 0.9x and 2.0. Those are using a light XML code and are the easiest to understand.
Syndication has different types of use, but always it is connected with some types of readers. There are AJAX readers like Google Reader, PHP and ASP readers or even standard applications.