RE: [SOAP] In-memory WSDL cache for ext/soap (was: [SOAP] Frequent crashes in multithreaded webserver sincenew WSDLcaching code in ext/soap)
| From: | Dmitry Stogov | Date: | Thu, 20 Apr 2006 06:33:21 +0000 |
| Subject: | RE: [SOAP] In-memory WSDL cache for ext/soap (was: [SOAP] Frequent crashes in multithreaded webserver sincenew WSDLcaching code in ext/soap) | ||
| References: | 1 | Groups: | php.soap |
| Request: | Send a blank email to php-soap+get-2242@lists.php.net to get a copy of this message | ||
I agree with Ilia's decision to wait for 5.2.
We will have more time for conceptual improvements and testing.
Both WSDL_CACHE_BOTH and WSDL_CACHE_ALL are not excellent.
May be WSDL_CACHE_ALL is little bit better.
You already can use bitwise operations. Now WSDL_CACHE_BOTH is
WSDL_CACHE_MEMORY | WSDL_CACHE_DISK.
You are welcome with suggestions and ideas.
I haven't a lot of time for ext/soap. :(
Also I don't use soap by myself so suggestions from real users may help.
Thanks. Dmitry.
> -----Original Message-----
> From: Adam Maccabee Trachtenberg [mailto:adam@trachtenberg.com]
> Sent: Wednesday, April 19, 2006 8:57 PM
> To: Dmitry Stogov
> Cc: 'Uwe Schindler'; 'Andrei Zmievski'; soap@lists.php.net;
> 'Andi Gutmans'; 'Rasmus Lerdorf'; internals@lists.php.net
> Subject: Re: [SOAP] In-memory WSDL cache for ext/soap (was:
> [SOAP] Frequent crashes in multithreaded webserver sincenew
> WSDLcaching code in ext/soap)
>
>
> On Wed, 19 Apr 2006, Dmitry Stogov wrote:
>
> > Now you can enable disk and/or memory cache through configuration
> > directive "soap.wsdl_cache" in php.ini. It can have one of the
> > following values WSDL_CACHE_NONE, WSDL_CACHE_DISK,
> WSDL_CACHE_MEMORY,
> > WSDL_CACHE_BOTH. The default value is WSDL_CACHE_DISK for backward
> > compatibility.
>
> Can we change WSDL_CACHE_BOTH to WSDL_CACHE_ALL to prevent
> problems if we add a third method of WSDL caching? Ideally,
> we'd also use bitwise operators here, similar to error reporting:
>
> WSDL_CACHE_MEMORY | WSDL_CACHE_DISK
>
> > BTW the patch is not trivial, it had a lot of bugs and may
> be not all
> > of them are found. So we need to decide if this feature should go
> > into 5.1.3 or only into next release.
>
> I would prefer not to break ext/soap, so I suggest 5.2.0. My
> main reason for delaying is that this does not add any new
> functionality: it's "only" performance improvements. People
> who really need it can run latest CVS.
>
> -adam
>
> --
> adam@trachtenberg.com | http://www.trachtenberg.com
> author of o'reilly's "upgrading to php 5" and "php cookbook"
> avoid the holiday rush, buy your copies today!
>
>