MS web services are document-styled web services. But you still have the overhead of (de)serializing your XML request to parameters.
When you have a service which takes 5 parameters as input, you would have to deal with the (de)serializing/mapping of the XML to 5 different parameters. Instead if you want to map your XML request to a "Document" object, you would be circumventing the overhead of these many (de)serializations but you would have the overhead of custom marshalling of the raw XML which I think is considerable.
I understand that Microsoft uses Doc-style as default SOAP binding. But how does the mapping of XML to COM objects occur? I have a very vague idea of Microsoft's web services, please correct me if I am wrong.
Document styled web services in .NET differ only in the way SOAP requests are formatted BUT the underlying mechanism is similar to a RPC styled web service. In .NET web services you could use SOAP extensions to intercept the incoming SOAP requests and map them to objects.
Can anyone help me in elucidating the REAL difference between Doc and RPC styled web services and the lower level implementation?
How does Axis implement the message styled web services in terms of (de)serialization? Do they differ only in terms of message validation using schema?
Thanks, Vivek
From: "Pridemore, Russell (MAN-Corporate)" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> Subject: RE: Document (Vs) RPC style services Date: Tue, 30 Mar 2004 13:20:37 -0500
I was looking into interoperability with MS web services and discovered that MS supports doc, but not RPC. However, it appears that RPC is a subset of doc, so it is possible to convert a WSDL from RPC -> document.
Anyway, the point is that there shouldn't be any measurable difference between the two communication styles, unless I'm missing something. ;-)
Russ
-----Original Message----- From: Vivek Nagulapati [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 1:09 PM To: [EMAIL PROTECTED] Subject: Document (Vs) RPC style services
Hello All,
I am doing a performance evaluation between Document and RPC style web services. Below are two of the criteria I would be evaluating.....
i) Requests/Sec served (Vs) Payload size ii) Time taken to process a single request (Vs) Variable Payload Size
Can anyone think of any better criteria to evaluate?
Thanks a lot, Vivek
_________________________________________________________________ Get reliable access on MSN 9 Dial-up. 3 months for the price of 1! (Limited-time offer) http://join.msn.com/?page=dept/dialup&pgmarket=en-us&ST=1/go/onm00200361ave/ direct/01/
_________________________________________________________________
All the action. All the drama. Get NCAA hoops coverage at MSN Sports by ESPN. http://msn.espn.go.com/index.html?partnersite=espn
