- From: William Morris <me@williammorris.com>
- Date: Mon, 10 Feb 2003 18:40:17 -0500 (EST)
- To: <xml-dist-app@w3.org>
I dont know if it is too late, but I would like to offer the following text as a proposed addendum to SOAP Version 1.2 Part 0: Primer ---- N.n SOAP over SSH SSH offers an alternative means of transfer for SOAP messages in enviroments where security is a concern, or system resources do not allow for a full webserver. The example below, like that of 3.2 SOAP over email, should not be construed as being the standard way to carry SOAP messages. The SOAP version 1.2 specifications do not specify such a binding. Example n shows the travel reservation request and response messages from Example 1 and Example 2 passed thru a program on a remote server for processing. Example n ssh -l travel travelcompany.example.org /usr/local/travel/bin/Reservations --name John%20Q.%20Public < request.xml > response.xml SOAP message from Example 1 carried in a file named request.xml and the response from Example 2 returned in a file named response.xml Command line parameters are encoded to prevent conflicts with shell escape characters. The exit status of the remote command is required to be passed by the ssh client. The remote commnd is required to exit 0 on success, and >0 if an error occurs, to identify errors that occur during processing. An exit status of 255 indicates a ssh client error occured. ---- The html version of the above is available at http://www.williammorris.com/soap/soapoverssh.html -Bill
Received on Monday, 10 February 2003 18:41:00 UTC