Re: [Soaplite-devel] SOAP::Client

[Robert L. <rla...@ao...>]

Paul Kulchenko wrote:
> Martin/Rob,
> 
> As far as I remember, this was to allow someone to create objects
> with:
> 
> CLASS->endpoint(...)
> 
> rather than
> 
> CLASS->new->endpoint(...)
> 
> with both $obj->endpoint(...) and $obj->new->endpoint(...) still
> working as expected.
> 

What follows is opinion, and not a change request.

I've always found CLASS->method to be very confusing to use.  I also 
find object nesting confusing... i.e. 
CLASS->method(args)->other_method()->result.

I think the loose object model actually leads to more confusion rather 
than making the module easier to use, because theres just TOO MANY ways 
to do the same thing.  And when following a standard protocol, in this 
case SOAP, having lots of different interpretations really defeats the 
purpose.

The LWP method of creating multiple objects for your user agent and 
envelope is more along the lines of what I would expect with a SOAP 
implementation.  This would also allow for error checking at different 
levels of the transport, something I've never quite managed to get right 
with SOAP lite.

Rob