ОТН: [PHP-WIN] Utilizing the file cache on PHP 7.2

Hi again,

-----=F0=DF=D2=D7=CF=CE=C1=DE=C1=CC=CE=CF =
=D3=DF=CF=C2=DD=C5=CE=C9=C5-----
=EF=D4: [email protected] <[email protected]>=20
=E9=DA=D0=D2=C1=D4=C5=CE=CF: Monday, June 4, 2018 9:47 AM
=E4=CF: 'Anatol Belski' <[email protected]>; '[email protected]'
<[email protected]>
=EF=D4=CE=CF=D3=CE=CF: =EF=F4=EE: [PHP-WIN] Utilizing the file cache on =
PHP 7.2

Hi,

-----=F0=DF=D2=D7=CF=CE=C1=DE=C1=CC=CE=CF =
=D3=DF=CF=C2=DD=C5=CE=C9=C5-----
=EF=D4: Anatol Belski <[email protected]> =EF=D4 =C9=CD=C5=D4=CF =
=CE=C1 Anatol Belski
=E9=DA=D0=D2=C1=D4=C5=CE=CF: Sunday, June 3, 2018 8:19 PM
=E4=CF: [email protected]; [email protected]
=EF=D4=CE=CF=D3=CE=CF: RE: [PHP-WIN] Utilizing the file cache on PHP 7.2

Hi,

> -----Original Message-----
> From: [email protected] <[email protected]>
> Sent: Thursday, May 31, 2018 10:44 AM
> To: [email protected]
> Subject: [PHP-WIN] Utilizing the file cache on PHP 7.2
>=20
> Hello,
>=20
>=20
>=20
> I ran into a problem with the file cache with PHP 7.2.6
>=20
> I used to be able to predict the cache path
>=20
>=20
>=20
> .e.g
>=20
> opcache.file_cache=3DF:\SVN\xxx\5.2\cache
>=20
> opcache.file_cache_only=3D1
>=20
>=20
>=20
> That would result in the actual BIN files being stored here:
>=20
> F:\SVN\xxx\5.2\cache\cb30f97c420833336c52d76bb38c161\33f5bcdd9882d65b
> c27c038
> df49ec706\
>=20
>=20
>=20
> And with PHP 7.1 these would remain the same for every PHP sub=20
> version, regardless of the server it runs on
>=20
> Now with PHP 7.2 they will change if I run it on a different server
>=20
A couple of versions ago one more path segment has been added. Please =
check
zend_file_cache_get_bin_file_path() for more info. It affects 7.1, too.
Thus, even exporting the system_id to the PHP land wouldn't give a =
complete
solution. Hopefully that helps.

I'm not sure one should rely on how the path is put together. The =
system_id
will be different in every PHP build by version. As it's an internal =
detail,
it can change on demand and doesn't affect the user operation. The =
actual
change was needed for a bug fix.=20

Regards

Anatol=20

---------

I'm OK with it changing every build and every version as it will be =
handled
by packaging .. as long as I have a way of knowing it in advance

I was looking at the zend_file_cache.c when I submitted the bug. It was =
a
while back That bug is now invalid/pointless

I would love to have it work out of a sqlite database and have like a
handler interface for the cache, but that's pushing it I guess

Thank you Anatol
Regards,
Momchil

----------

I'm ditching the idea of using the file cache

It also used to be portable, but now the compiled files are looking for
includes that reside only on the system they were compiled on
That did not use to be the case

Momchil