A Review on Web Services and Security Issues

Abstract

In this paper we are discussing that data mining and scoring tool providers require users to use provider-specific ways to invoke their services. The provider-specific approach could be a major factor affecting why data mining tools and applications are not currently as widespread as one might hope. Web services standards can address these proprietary issues. This paper discusses what web services are, in general, as well as in the context of data mining and scoring. One not-so-rigorous description of web services is as follows: A web service client passes a request in text while the service provider acts on the request and returns text to the client, all via the Web. Web services are identical in concept to this process. However, complicated web services often involve richer content as input than simple web page browsing with web services. XML is most often used to format the input. As to the output, the contrast between web browsing and web services is not about whether or not the content is complicated, but rather whether the format is HTML or not. Even though it is not entirely technically correct, one can view an HTML document as an instance of an XML document. However, HTML is particularly designed for web browser consumption, while an XML document is designed for a specific business need. It wouldn’t be complete to describe web services without mentioning the SOAP protocol. Keep the following notes in mind if you are new to SOAP: SOAP is not really a simple protocol and “object” has nothing to do with the protocol. The Worldwide Web is based on the HTTP protocol. Currently the SOAP protocol fits nicely on top of the HTTP protocol.