SOAP Library

[Mark Smith]

In fact, for the main SOAP service that I use, I made a library that  
I have a few apps using. It's also an https situation, and I had  
problems with frequent timeouts (see bug 3639), so I use curl for the  
actual http side of it, so using the SOAP library wouldn't have been  
an option anyway, I think. It might be an interesting challenge to  
get a full WSDL based library together, but I don't think I'll be  
trying it just at the moment!

Best,

Mark

On 7 Oct 2007, at 05:13, Mark Wieder wrote:

> Mark-
>
> Friday, October 5, 2007, 4:57:22 PM, you wrote:
>
>> I work with a couple of SOAP services, and frankly, I'm with Dave in
>> not really seeing the point of it. It seems to be a sledge-hammer to
>> crack a nut.
>
>> The approach I take is to make template requests with placeholders,
>> store them in custom properties, copy them into variables and fill
>> them in and post them as necessary. I then have handlers to deal with
>> each type of response. It's quite a lot of work for a SOAP service
>> with a lot of different methods, but you only have to address the
>> particular methods you're interested in, and it works well. It
>> doesn't produce a generalised SOAP library though.
>
> I just posted a response to Dave before reading this one. Web services
> seem to be one of those Web 1.5 things that never really caught
> critical mass.
>
> And I do the same thing you do: storing templates in custom
> properties, then replacing key parameters before calling the library
> routines.
>
> -- 
> -Mark Wieder
>  mwieder at ahsoftware.net
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution