Peter Kruithof

Good question, I think setting the composer executable should be enough. Then again being able to set the php executable is maybe a more portable solution. I'm not sure.

Something you can already do: mark the package as [abandoned](https://getcomposer.org/doc/04-schema.md#abandoned) so installs will get a notification about this. You can also point to a replacement package, though I'm not sure...

I would be willing to work on something for this by the way, just wanted to see if there is any support for it first.

The PSR (and common implementations) only [explicitly mentions](https://www.php-fig.org/psr/psr-6/#data) that the value needs to be serialized: > Implementing libraries MUST support all serializable PHP data types, including: > > Strings -...

Agreed. We created a workaround for this by implementing a special `CacheItemPoolInterface` implementation, that expects the values to come from the `CachePlugin` (meaning an array with a `response`, `body`, etc.)....

What would be a possibility: if we inject something like a `BodySerializer` in the plugin, with the following api: ```php interface BodySerializer { public function serialize(StreamInterface $stream): string; public function...

Where would this `purge` method be called exactly? I don't see any invalidation logic in the plugin (besides setting the expiration date in the cache items).

I see now that the `StreamInterface` has a `isSeekable` method. We could simply use 1 file as described here: https://github.com/php-http/cache-plugin/issues/50#issuecomment-441596329 If the stream provided by the Serializer is non-seekable, the...

ping @b4b4r07 This is a big problem imo, is this being looked in to?

Maybe with crowdfunding? Looks like it costs [$80 a year](https://www.hover.com/tld/sh), I'll bet you can raise that with donations.