[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: SOAP for non-RPC messaging application
IMPORTANT: HUGHES SOFTWARE SYSTEMS LTD. (HSS) IS NOW FLEXTRONICS SOFTWARE SYSTEMS LTD. (FSS) Hello, Thanks for your earlier response. Starting from HTTP/1.1, there is now a support for "persistent" HTTP connections where a server/client can decide to close the underlying transport (TCP) explicitly (by including `Close' connection tag in Connection header) otherwise it is assumed that underlying TCP connection would remain allowing multiple request/responses to be exchanged on the same connection. My requirement will be fulfilled if any open source SOAP framework allows me to build a SOAP client/server pairs that exchange SOAP messages on persistent HTTP connections. Of course, the assumption here is that both ends support HTTP/1.1. Thanks and best regards, Sapta Girisa.
Assuming you would be using SOAP over HTTP (the most likely assumption), the TCP connections would be maintained for the duration of a single HTTP request/response exchange, and then terminated. HTTP itself is "reliable" only to this degree due to its underlying TCP support - that is, it is reliable only on a per-message basis, and not between messages. Additional reliability can be gained by using a vendor product (such as a MOM product), or implementing a reliable messaging standard such as OASIS WS-Reliability. So in order to achieve the sustainment of the TCP connection in your flow figure, you would need to employ such reliability means. Please see [1] for an article on OASIS WS-Reliability that I published in Nov. 2003. Responding to your question #1: SOAP is not just for RPC - that was its originally conceived usage, but it has since expanded. From [2]: "As mentioned in section http://www.w3.org/TR/soap12-part2/#datamodel, use and implementation of the SOAP RPC Representation is OPTIONAL." See [2] also for a description of SOAP 1.2 message exchange patterns (MEPs). Essentially you will need to match each of your 2 message exchange depictions with a SOAP MEP. Additionally, WSDL 1.1[3] specifies 4 "transmission primitives" that an endpoint can support: - One-way - Request/response - Solicit/response - Notification The first message exchange in your figure below would be a request/response, while the second would be a solicit/response. Hope that helps. [1] http://www.webservices.org/index.php/ws/content/view/full/47407 [2] http://www.w3.org/TR/soap12-part2/#soapsupmep [3] http://www.w3.org/TR/wsdl#_one-way Kind Regards, Joseph Chiusano Booz Allen Hamilton Visit us online@ http://www.boozallen.com/ From: saptagirisa.n@f... [mailto:saptagirisa.n@f...] Sent: Thursday, March 31, 2005 2:05 AM To: xml-dev@l... Subject: SOAP for non-RPC messaging application I am an absolute novice to SOAP/XML and have been trying to make sense out of the cryptic W3C SOAP specifications. I have a requirement to build SOAP/XML based message interface between two network nodes (not in anyway related to any webservice kind of stuff). The requirement is two have both client/server implementation on both sides and a typical flow would be like this : [Node A] [Node B] |==========TCP Connection Establish=========>| |---------------------- Request 1 (SOAP) --------------------->| |<-------------------- Response 1 (SOAP)---------------------| |<-------------------- Request 2 (SOAP) -----------------------| |---------------------- Response 2 (SOAP)------------------->| |==========X TCP Connection Closure X========| Here you can notice that a TCP connection is established first, SOAP messages are exchanged back and forth, request can be sent by either node. I have these questions : 1. Most of the literature I have gone through talks of SOAP for RPC based applications. Can I use SOAP for a non-RPC kind of application (for instance purely for peer-2-peer message transfer as explained above - where within the same TCP session multiple request/response messages are exchanged back and forth.) 2. Is there any License free SOAP framework that allows me to build a SOAP client cum server to achieve the above. I would be grateful if you can suggest a way out. Thanks in advance. Best regards, S.Girisa. *********************** FSS-Unclassified ***********************
*********************** FSS-Restricted ***********************
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|