Re: Two SOAP Issues

Christian Dickmann wrote:

I've been thinking about this. The purpose of the soap library is to serialize and unserialize data to/from soap messages and provide transports for them. I think it's unwise to anticipate that any given application is going to want the data transformed automaticaly after serialization. I think it's best to leave the data as-is, and let the application make the decision what to do with it.

What about adding a Config-var? $soapclient->setMode("transform"); or something like that. Christian Dickmann

Hmm, but what if I want data type X transformed, but I don't want data type Y transformed? If I have to call setMode for each type, I might as well just do the conversion at the application level. What we could do is flesh out the data types (SOAP/Types) further, and then have an option to return those classes rather than a plain PHP type. Then we could have $type->as_*() type functions that can convert the type to various formats. But it's that much a better solution. I think coming up with a solution for this is a good thing, but I don't realy want to do it at the serialization level if we can avoid it. Shane