Re: [SOAP] php-soap interop

--- Shane Caraveo <shane@caraveo.com> wrote: > > >>> > >>> What I am missing so far is how I define SOAPStruct is in the > >>> namespace http://soapinterop.org/xsd. If soapvar > >>> was changed to > >>> accept something like: > >>> > >>> return > >>> SoapVar($retobj,'{http://soapinterop.org/xsd}SOAPStruct'); > >> > >> > >> Again.. if you server isn't using soapenc:Struct for any struct > >> encoding then > >> ALOT of the time it would use a wsdl. And when using wsdl's all the > >> type stuff, > >> encoding and ns are all behind the scenes. > > > > > > Based on the premise of always parsing wsdl at run-time I would agree > > with you. But for any possibility of generating proxies or wrappers > > based on wsdl, it's an important item. > > > > Just another note, I'm not realy against the server side needing to have > wsdl available, but having that on the client side is more an issue > since clients may be loaded/unloaded more often. Never thought of that... So instead of parsing a wsdl you are suggesting of autogenerating a php class that will do all of the manipulation of the encoding not the soap-engine. For the sole purpose of not wanting to re-parse/download a wsdl? I would rather see client side caching of wsdl's. Way more convient and more transparent than auto-generating php files based on a wsdl that could change peridocially. FYI: php-soap does cache parsed wsdls. The client and server acually share the cached wsdls. Not in shared memory or anything, so they are cached per process. I totally agree/understand wsdl is not dependant on soap nor is soap dependant on soap. But the fact is pretty much every (or all) usefull services out there uses wsdl's. Im not against changing soapvar or the engine to accomidate this. I was just trying to explain why i did what i did. - Brad __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com