May 3rd, 2011
If you read our article a couple weeks back about dynamically changing the WSDL URL via SoapServer you may have thought, there’s little value here, since I use Zend Framework or NuSoap to publish Soap Services with PHP. This article explores a more prevalent issue with the design of SoapServer and the problem can’t be solved with a subclass of SoapServer. The problem we explore in this article is the design of the classes you would use to handle Soap actions. These classes and objects are designated by the SoapServer setClass and setObject methods. We’ll refer to them as Provider Classes in this article.
April 14th, 2011
Asynchronous Message Exchange Patterns
Asynchronous MEP’s bring many concepts from asynchronous OS development to the Internet. One aspect that’s interesting is the perceived speed up clients feel from asynchronous operations. This where the terminology non-blocking comes from, the idea being the client says, “contact me when its finished” as it submits a request. It’s like dropping clothes off at the cleaners; the request is going to take a few days to complete. The service provider says ‘no problem’ and the client is off to focus on other things while the long running request is handled by the provider.
April 9th, 2011
Services need to be portable
So you’ve started using PHP’s SoapServer class with hand built or pre-generated .wsdl files. Great, you’ve got a Soap service running on a development machine! Upon deploying the service in a different environment clients are submitting requests to the development machine, what happened?