Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81822
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain rodas.me designates 109.74.200.116 as permitted sender)
Message-ID: <54D2454D.40707@rodas.me>
Date: Wed, 04 Feb 2015 13:14:05 -0300
MIME-Version: 1.0
To: internals@lists.php.net
References: <54D1593A.3000607@rodas.me> <00e001d0404a$dea88cd0$9bf9a670$@tekwire.net>
In-Reply-To: <00e001d0404a$dea88cd0$9bf9a670$@tekwire.net>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="aK1DJkN28D95xv6xDhQfPRhnQPfvr4Ini"
Subject: Re: [PHP-DEV] Question regarding stream wrappers and op code cache
From: cesar@rodas.me (Cesar Rodas)

--aK1DJkN28D95xv6xDhQfPRhnQPfvr4Ini
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 04/02/15 04:19, Fran=C3=A7ois Laupretre wrote:
>> De : Cesar Rodas [mailto:cesar@rodas.me]
>> I have a doubt, is it efficient include/require files from a source
>> different than the "real file system" a stream wrapper class? My
>> question is, would the op-code cache work as it would when reading a
>> file form the filesystem?
> I understand your question but, yes, the feature is essential to packag=
es systems like phar and phk (and it is useless for most other stream wra=
ppers). Package systems distribute a virtual file tree, handle stat(), an=
d returning valid mtimes. So, the opcode cache must be able to work with =
these stream wrappers.
I'm working on a project to *put* all generated code inside a single
file (and expose through "generated://doctrine" or
"generated://<package-name>") but it's pointless if the compiled op-code
is not cached :-(

I believe this https://wiki.php.net/rfc/streams-is-cacheable would be
brilliant!

Cheers,
>
> Regards
>
> Fran=C3=A7ois
>
>

--=20
C=C3=A9sar D. Rodas
Open Source developer
+595-983-161124
PGP: F9ED A265 A3AB C8A1 D145 7368 158A 0336 C707 0AA6



--aK1DJkN28D95xv6xDhQfPRhnQPfvr4Ini
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJU0kVNAAoJEBWKAzbHBwqmWd8QAMWezhQ+NJQwgOJshMeELCJ5
y3yjVFUcFyLFfmTUtG0BnGu8A+Pw3PR2xHj/kFf2KjhfZHMx5DO+0q3vPYAd+Ny7
Z/ET4RGGjf5ohYFgnVeupEoOg9Sw0t+BuSM0Rcrzd9voYKBMyImq3QpnOpyhwSFh
G85n3toYWMEarVnJkGco6w9O8IRN/YHc30yp0VeZ54j1P1dxmAc0ei0GJqyh/hWA
3i7htfKc8k40Iy7th7NCD4D2VGrfNCJcRXexZlSYTvBxbIUnE+7HaBxkbuPp6P5C
GA8OCzldnHnhze7NFLnekpBOxLuD2N84b1IaI85P7IAV3zVbBmY8rwp3zX7WTJYC
c+B/MHwwnRI+/ycar3fgGA0uJkyEKfwS8ZAEjp55ppi3qddtumlE6/bC5WZdkmHd
V8JSAa409ECbw51l5o2V2UC+fbm+i/C7yTYSqAxJifQE1SP/Up27Esl+TcYuDsos
cJWH+R9xz6YsM+XwyX5wipefc52skOowr/m7NB3NnQxyszsZPnrn+BByvcS6sEBF
Wh1qhtTYp8iv2RBia3dBkeT+g/jtuRfFPTln6G11Pqx2urJkaO8TyUKm/pCbwyxa
YqHZxsSWYnnEPx7EMcXX7rMiaAdCJvFcYzSvL6sJdB9rDSuudWmGujX28wzinnEz
faBoPsnFwhR8hU+IUMFG
=1zTf
-----END PGP SIGNATURE-----

--aK1DJkN28D95xv6xDhQfPRhnQPfvr4Ini--