On Jul 28, 2005, at 9:10 AM, Zeev Suraski wrote:
At 01:50 AM 7/28/2005, Ilia Alshanetsky wrote:
Are you therefore saying SOAP support should be 100% diabled when
allow_url_fopen is off?
SOAP is not disabled, simply prevented from querying remote data
sources directly.
What exactly can you do with it other than query remote data sources?
I tend to agree with Adam (and I guess Wez) - SOAP should not be
affected by allow_url_fopen. We can have another directive,
allow_web_services_clients or whatever, that will affect SOAP
instead. The average user will have no idea that allow_url_fopen
is in any way related to web services.
I think we should namespace them per extension:
soap.allow_url_fopen (or something more inspired). This will allow
you to toggle it on a per-extension basis easily.
That having been said, in the current implementation this should
probably only affect the pulling of the WSDL file, right (since
currently the actual client request is done through a non-streams
implementation). You can certainly have a local WSDL file.
George
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
