Re: Is there a future for RPC style SOAP?
Dick Brooks <[email protected]> Sat, 7 Dec 2002 11:02:54 -0700
| Newsgroups | gmane.comp.windows.devel.soap.general |
|---|---|
| Message-ID | <[email protected]> |
Anne wrote: >I'm not sure I really see much value for the SOAP RPC structure if you're >not using SOAP encoding. This was the same conclusion reached by the ebXML Message Service team when SOAP was being integrated into ebMS. The ebMS specification contains header elements to identify "Service" (aka Object) and "Action" (aka Method) to support both RPC and messaging exchange models. The team of people responsible for integrating SOAP/ebMS saw no added value in replacing ebXML's model with SOAP's RPC model. Here is a snippet showing ebXML's approach to identify RPC's: Healthcare Example: <Service>ClaimProcessing</Service> <Action>ProcessInstitutionalClaim</Action> Energy: <Service>CapacityScheduling</Service> <Action>ProcessNomination</Action> I chose to show these two examples specifically because the parameters passed to both contain "X12" data. Dick Brooks Systrends, Inc 7855 South River Parkway, Suite 111 Tempe, Arizona 85284 Web: www.systrends.com <http://www.systrends.com> Phone:480.756.6777,Mobile:602-684-1484,eFax:240-352-0714 -----Original Message----- From: Discussion of implementing SOAP applications today [mailto:[email protected]]On Behalf Of Anne Thomas Manes Sent: Saturday, December 07, 2002 6:16 AM To: [email protected] Subject: Re: [SOAP] Is there a future for RPC style SOAP? > Date: Fri, 6 Dec 2002 14:35:27 -0000 > From: "GOFFIN, Fraser" <[email protected]> > Subject: Re: Is there a future for RPC style SOAP? > > <snip> > So, despite the fact that RPC/Encoded is commonly used today I for > one will not implement anything further using SOAP encoding. This still > leaves the fact that there are some circumstances where implementing RPC > style exchange could be of use. Unfortunately there is little tool support > RPC/Literal so I guess its Doc/Lit only going forward ? > > Fraser. > I'm not sure I really see much value for the SOAP RPC structure if you're not using SOAP encoding. If you're not using SOAP encoding, then the only difference between RPC and Document style formats is that the RPC message is wrapped in an element that represents the method name. There are other ways to indicate the method you'd like to perform (e.g., the target URI, or the SOAPAction header). What circumstances were you thinking of where it could be of use? Anne You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.