Re: Re[4]: [PEAR-DEV] SOAP Objects..

> I really want to make the soap response to be a separate object. Right now > it's bundled in with another object. I am debating on weather the > transports should be other objects too. It may be an overkill and it may be > more straightforward to have the client have different methods like > > client->sendHTTP > client->SendSMTP > etc.. > > This approach works pretty well as long as the transport is simple enough > to fit into a function or two but maybe more cumbersome if the transport is > really tricky. Why not do something like the Logging or DB classes, where the client class is just static and you do something like: $client = XMLRPC::create('http'); // or $client = XMLRPC::create('https'); // etc. And there is a XMLRPC_client_common, and XMLRPC_client_http, etc. which just extend the common class? - Colin