If yours is a serious response, it seems that I failed to describe my problem:
The app isnīt just a remote services eater. It does a lot of things: database querying, file processing, data management, sessions, authentication, etc. But there are some points where data MUST come from a remote WSDL service, and these points have become dangerous bottlenecks, because when that remote server goes down o delays its response, ALL THE APPLICATION waits until that process reach timeout or serves the response.
If yours is a funny response, please start your own thread, prefixing it with a "JOKE" keyword, so we can choose to read it when bored.
I have also crossposted this problem in Stack Overflow and SOAP::LITE list, whith any luck.
Any help will be really appreciated: Miguel
|