Comments on: PHP SOAP vs. SDO http://www.trachtenberg.com/blog/2006/10/12/php-soap-vs-sdo/ Thoughts on PHP, eBay, and too many technical topics for my family's liking. Thu, 18 Feb 2010 23:21:22 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Greg Whitescarver http://www.trachtenberg.com/blog/2006/10/12/php-soap-vs-sdo/comment-page-1/#comment-23951 Greg Whitescarver Tue, 21 Nov 2006 20:30:25 +0000 http://www.trachtenberg.com/blog/2006/10/12/php-soap-vs-sdo/#comment-23951 SDO is still a baby. Performance is sure to improve over the next year or so, giving you just enough time to fix your WSDL ;-) When all is said and done, SDO is a lot more than a PEAR extension... you're comparing an apple to a fruit stand. Such an awesome abstraction between the class interface and the message protocol is exactly the kind of technology that is propelling the web forward as a distributed computing (read: "value") platform. By the way, thanks for a great presentation at Zend Conference 2006. SDO is still a baby. Performance is sure to improve over the next year or so, giving you just enough time to fix your WSDL ;-) When all is said and done, SDO is a lot more than a PEAR extension… you’re comparing an apple to a fruit stand. Such an awesome abstraction between the class interface and the message protocol is exactly the kind of technology that is propelling the web forward as a distributed computing (read: “value”) platform.

By the way, thanks for a great presentation at Zend Conference 2006.

]]> By: Adam Trachtenberg http://www.trachtenberg.com/blog/2006/10/12/php-soap-vs-sdo/comment-page-1/#comment-16000 Adam Trachtenberg Mon, 16 Oct 2006 21:14:40 +0000 http://www.trachtenberg.com/blog/2006/10/12/php-soap-vs-sdo/#comment-16000 Hello Graham -- I'm glad my post was useful -- I am still exploring everything you can do with SDO, so I am really just stumbling around for now. I'm familiar with ext/soap's classmapping feature -- I'm using it now with the eBay API to create my interface. Can you provide me with a simple PHP 5 code example of how I might be able to hook into this using SDO as part of a Web services client? I won't worry for now about double WSDL parsing and performance. That's something that I'm sure can be worked out, particularly given that ext/soap can store a parsed WSDL file in memory if speed is critical. (That patch came from Yahoo!, so I am sure it is "fast enough" for most people.) I bet SDO could leverage that (or steal some ideas from it) if things came down to it. Besides, our WSDL is so large that it's often a good test for regressions and performance. I know a number of other Web services tools companies and applications have found it useful. I think Borland includes it as part of their unit testing for Delphi. -adam Hello Graham –

I’m glad my post was useful — I am still exploring everything you can do with SDO, so I am really just stumbling around for now.

I’m familiar with ext/soap’s classmapping feature — I’m using it now with the eBay API to create my interface. Can you provide me with a simple PHP 5 code example of how I might be able to hook into this using SDO as part of a Web services client?

I won’t worry for now about double WSDL parsing and performance. That’s something that I’m sure can be worked out, particularly given that ext/soap can store a parsed WSDL file in memory if speed is critical. (That patch came from Yahoo!, so I am sure it is “fast enough” for most people.) I bet SDO could leverage that (or steal some ideas from it) if things came down to it.

Besides, our WSDL is so large that it’s often a good test for regressions and performance. I know a number of other Web services tools companies and applications have found it useful. I think Borland includes it as part of their unit testing for Delphi.

-adam

]]> By: Graham http://www.trachtenberg.com/blog/2006/10/12/php-soap-vs-sdo/comment-page-1/#comment-15968 Graham Mon, 16 Oct 2006 14:10:07 +0000 http://www.trachtenberg.com/blog/2006/10/12/php-soap-vs-sdo/#comment-15968 Hi Adam, I'm really glad you found the time to take a look at SDO and give it a try with the eBay API. Your feedback is very helpful and gives us a few areas to focus on. Some specific comments below: >> However, it will not directly consume a SOAP message because >> the WSDL doesn’t include any mention of the SOAP envelope wrapper. In PHP 5.2 ext/soap has been extended to support a typemap capability. This can be used to register serialization/deserialization functions for each complex type on the Web service interface. We use this in our Service Component Architecture (see http://osoa.org/display/PHP/SCA+with+PHP) implementation to enable SDOs to be used for complex types on Web service calls. The typemap functions get called by ext/soap to convert between the xml for a complex type and an object (in our case an SDO). The big downside to this approach is that currently the WSDL will be loaded twice! - once by ext/soap and once by SDO. This doesn't bode well for large WSDLs, based on your later comments around performance. >> Oddly, this corresponds perfectly with our “XML API,” so I could use >> that to retrieve properly formatted data that I can pass directly to >> SDO. This sounds like something we'd like to give a try :-) >> When I feed that to SDO, it takes 8.5 seconds to process the XML >> Schema data. Yikes! Yikes indeed! Thanks for pointing this out. Performance is not something we've had any feedback on previously, so the eBay scenario will help us a lot here. Cheers, Graham. Hi Adam,

I’m really glad you found the time to take a look at SDO and give it a try with the eBay API. Your feedback is very helpful and gives us a few areas to focus on. Some specific comments below:

>> However, it will not directly consume a SOAP message because
>> the WSDL doesn’t include any mention of the SOAP envelope wrapper.

In PHP 5.2 ext/soap has been extended to support a typemap capability. This can be used to register serialization/deserialization functions for each complex type on the Web service interface. We use this in our Service Component Architecture (see http://osoa.org/display/PHP/SCA+with+PHP) implementation to enable SDOs to be used for complex types on Web service calls. The typemap functions get called by ext/soap to convert between the xml for a complex type and an object (in our case an SDO).

The big downside to this approach is that currently the WSDL will be loaded twice! – once by ext/soap and once by SDO. This doesn’t bode well for large WSDLs, based on your later comments around performance.

>> Oddly, this corresponds perfectly with our “XML API,” so I could use
>> that to retrieve properly formatted data that I can pass directly to
>> SDO.

This sounds like something we’d like to give a try :-)

>> When I feed that to SDO, it takes 8.5 seconds to process the XML
>> Schema data. Yikes!

Yikes indeed! Thanks for pointing this out. Performance is not something we’ve had any feedback on previously, so the eBay scenario will help us a lot here.

Cheers, Graham.

]]>