Originally posted by Amey Samant:
Unfortunately there is hardly any information on net with respect to CIM-XML and webservices.
Sometimes there seems to be the unstated convention that "web services" refers to "XML-over-HTTP", while "Web Services" refers to "SOAP-over-HTTP". And the definitions for CIM-XML that are provided at the link you left aren't sufficient for "Web Services" which require XML Schema - DTDs cannot be used.
Originally posted by Amey Samant:
also is there any restriction on request/response to/from webserivce?
Response by William Brogden:
Any web service using HTTP for request/response has to correctly read and create HTTP headers if thats what you mean. Reading the body of a request and creating the body of a response is the responsibility of a toolkit such as Axis.
While WSDL can express 4 transmission primitives (One-way, Request-response, Solicit-response, and Notification) a binding to HTTP as the transport protocol limits the
exchange pattern to Request-Response. "One way" is implemented with a SOAP binding (as the message protocol) by including the SOAP request in the HTTP request but not returning a SOAP response with the HTTP-response. Because of these limitations some work-arounds exist:
Asynchronous operations and Web services, Part 1: A primer on asynchronous transactions Asynchronous operations and Web services, Part 2 Note that these work-arounds can be used with non-SOAP web services as well - however they always imply that there is a Web Server (responsible for responding to an HTTP-request) on both ends of the "conversation".