php-rss-bridge/lib/CacheInterface.php

<?php

interface CacheInterface
{
    public function get(string $key, $default = null);

    public function set(string $key, $value, int $ttl = null): void;

    public function delete(string $key): void;

    public function clear(): void;

    public function prune(): void;
}
[lib] Split Bridge/Cache/Format into one file per class The files have grown to a size where it is necessary to search for a class in a file. This commit splits the content into one file per class. RSS-Bridge will require implementations and the implementations will require (once) the interfaces. 2016-09-05 18:05:19 +02:00			`<?php`
Reformat codebase v4 (#2872) Reformat code base to PSR12 Co-authored-by: rssbridge <noreply@github.com> 2022-07-01 15:10:30 +02:00
[core] Apply common indentation All files are now using tabs for indentation 2016-09-10 20:41:11 +02:00			`interface CacheInterface`
			`{`
fix: rewrite and improve caching (#3594) 2023-09-10 21:50:15 +02:00			`public function get(string $key, $default = null);`
caches: Refactor the API (#1060) - For consistency, functions should always return null on non-existing data. - WordPressPluginUpdateBridge appears to have used its own cache instance in the past. Obviously not used anymore. - Since $key can be anything, the cache implementation must ensure to assign the related data reliably; most commonly by serializing and hashing the key in an appropriate way. - Even though the default path for storage is perfectly fine, some people may want to use a different location. This is an example how a cache implementation is responsible for its requirements. 2019-04-29 20:12:43 +02:00
fix: rewrite and improve caching (#3594) 2023-09-10 21:50:15 +02:00			`public function set(string $key, $value, int $ttl = null): void;`
caches: Refactor the API (#1060) - For consistency, functions should always return null on non-existing data. - WordPressPluginUpdateBridge appears to have used its own cache instance in the past. Obviously not used anymore. - Since $key can be anything, the cache implementation must ensure to assign the related data reliably; most commonly by serializing and hashing the key in an appropriate way. - Even though the default path for storage is perfectly fine, some people may want to use a different location. This is an example how a cache implementation is responsible for its requirements. 2019-04-29 20:12:43 +02:00
fix: rewrite and improve caching (#3594) 2023-09-10 21:50:15 +02:00			`public function delete(string $key): void;`
lib: Add API documentation 2018-11-16 21:48:59 +01:00
fix: rewrite and improve caching (#3594) 2023-09-10 21:50:15 +02:00			`public function clear(): void;`
lib: Add API documentation 2018-11-16 21:48:59 +01:00
fix: rewrite and improve caching (#3594) 2023-09-10 21:50:15 +02:00			`public function prune(): void;`
[lib] Split Bridge/Cache/Format into one file per class The files have grown to a size where it is necessary to search for a class in a file. This commit splits the content into one file per class. RSS-Bridge will require implementations and the implementations will require (once) the interfaces. 2016-09-05 18:05:19 +02:00			`}`