Re: Two SOAP Issues

Dietrich Ayala wrote:

I brought the class up to the point at which it was functional for my needs, but haven't worked on it since last fall. I don't know if Shane did any development on the server class when he PEAR-ified it. Number one on the to-do list would be a security audit :) The first version of the server required that the user call a method that 'registered' each function to be exposed as a service. The server would then deny requests for functions that weren't 'registered'. This wasn't very popular, I got lots of requests to not make this mandatory. I think that it should be mandatory by default in PEAR, and maybe have a class level variable in the server to toggle it. If/when the server gets WSDL generation added, then service registration will be mandatory if the user wants the functions to show up in the WSDL.

I'm addressing this by requiring the use of registered functions (without option to ignore) OR objects. With registered objects, you don't need to register each function in the object. Though I may make that a requirement or option also, haven't decided yet. Shane