Did you mean to omit the “return” for is_cacheable_stream_path if !PHP_STREAMS_SUPPORT_IS_CACHEABLE?
https://github.com/flaupretre/php-src/commit/d012ba6cb357df9fcb8f6669e3c7103018590b41?diff=unified#diff-f6d4b551c6233faa294ae9a97897c7d4R143 <https://github.com/flaupretre/php-src/commit/d012ba6cb357df9fcb8f6669e3c7103018590b41?diff=unified#diff-f6d4b551c6233faa294ae9a97897c7d4R143> > On Jan 4, 2015, at 8:13 AM, François Laupretre <franc...@tekwire.net> wrote: > >> De : Andrea Faulds [mailto:a...@ajf.me] >> How would cache invalidation work? Is there already some mechanism to >> handle that with streams? > > Sorry, I am not sure I understand what you mean with 'cache invalidation'. > Do you mean stat/mtime check to detect file changes ? This mechanism works > the same with stream wrappers through an url_stat() call. > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >
