Re: Run Time Cache RFC
| From: | Christopher Jones | Date: | Mon, 24 May 2010 20:46:43 +0000 |
| Subject: | Re: Run Time Cache RFC | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48453@lists.php.net to get a copy of this message | ||
Thanks Dmitry - that's great.
Also thanks to Stas for his reply.
Chris
Dmitry Stogov wrote:
Hi Chris, I've added notes for extension maintainers. I hope they will answer all your questions. Thanks. Dmitry. Christopher Jones wrote:-- Email: christopher.jones@oracle.com Tel: +1 650 506 8630 Blog: http://blogs.oracle.com/opal/ Free PHP Book: http://tinyurl.com/ugpomhomeDmitry Stogov wrote: http://wiki.php.net/rfc/runtimecache The patch breaks binary and source compatibility but it's not hard to adopt extensions to use it.It's clear from the patch. The same is explained in RFC in human language, but it's not so exact :)Hi Dmitry, Can update the RFC to explain the breakage andThe RFC should give enough explanation so (i) extension maintainers can immediately identify if their extension is going to be affected (ii) readers know where to look in the patch to get more details. If I understand what you implied later in your email, calls to zend_hash_copy should be replaced with calls to object_properties_init. Is this always true? Is this the only extension requirement? What happens if extensions don't do this - will it break or be a performance loss? I must be looking at a different RFC because there's nothing I can see that mentions any of these things. Chris