Webservices SOAP messages (SOAP uses XML to send messages back and forth), so your server must understand SOAP and any extensions that you want to talk about between them, and they are likely (but not necessarily) to infect WMDL files (which "explains" the various service endpoints and remote functionality). Usually we call this SOAP / WS- * stack with an emphasis on "stack", since there are several bits of software that should be available, and the more complex SOAP calls, the more this stack needs to be available and supported.
POST, , RESTful behaviors, HTTP. POST , , XML, , , POST HTTP . - , , , - HTTP-. , . HATEOAS , , SOAP, ; HTTP , . SOAP , ----stuffed kinda . ( , . , SOA ROA.:)
, "", : " , , , , , , , (), , ". Eh, .
, , SOAP - ; SOAP - , , , HTML, . HTTP , SOAP XML. SOAP HTML? , , , SOAP HTTP (, , , ), HTTP , , . , HTTP (, SOAP), , .
- , . webservices ( , 1200 ), , (.. , ) POST ( GET) . HTTP, , , , HTTP- , , , application/xml + myformat (, , application/x-xml + myformat, ). , 200, .
. (WS- * stack) , . - , .