SoapRobot

[SoapRobot at server.example.com]

<?xml version=3D"1.0" encoding=3D"UTF-8"?> 
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:SOAP-ENC=3D"http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" 
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"> 
<SOAP-ENV:Body> 
<m:echoStringResponse xmlns:m=3D"http://soapinterop.org/"> 
<return>A human being should be able to change a diaper, plan an invasion, 
butcher a hog, conn a ship, design a building, write a sonnet, balance 
accounts, build a wall, set a bone, comfort the dying, take orders, give 
orders, cooperate, act alone, solve equations, analyze a new problem, 
pitch manure, program a computer, cook a tasty meal, fight efficiently, 
die gallantly. Specialization is for insects. --Robert A. Heinlein</return> 
</m:echoStringResponse> 
</SOAP-ENV:Body> 
</SOAP-ENV:Envelope> 


6. Security Considerations 
Clients may wish to authenticate the sender's response in some API-specific way, as there is no direct connection between client and server and the server's response is trivially spoofed. 


7. References 

[0] Cunnings R., Fell S., Kulchenko P., "SMTP Transport Binding for SOAP 1.1", 2001 

[1] Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn, N., Nielsen, H. F., Thatte, S. and D. Winer, "Simple Object Access Protocol (SOAP) 1.1", May 2000. 

[2] Horton M., Adams R., "Standard for Interchange of USENET Messages" RFC1036, December 1987 

[3] Bradner S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, Harvard University, March 1997 

[4] Christensen E., Curbera F., Meredith G., Weerawarana S. "Web Services Description Language (WSDL) 1.1", March 2001.