Download the PHP package wp-oop/transient-cache without Composer
On this page you can find all versions of the php package wp-oop/transient-cache. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download wp-oop/transient-cache
More information about wp-oop/transient-cache
Files in wp-oop/transient-cache
Package transient-cache
Short Description A PSR-16 wrapper for WP transients.
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package transient-cache
WP Transient Cache
A fully compliant PSR-16 wrapper for WP transients.
Details
A common means of caching values in WordPress is by using transients. However, this approach suffers from several problems:
- Coupling to WordPress. You can't just suddenly substitute the caching mechanism you are using for another mechanism, and everything still works.
- No namespacing. All transients live in the same namespace, and independent consumers cannot reliably use arbitrary keys without the risk of possible conflict.
- No true modularity. Due to the above, if your application is modular, it cannot decide which caching mechanisms to use for what, because that would have already been decided by your modules.
- Missing features. For example, it is not possible to clear all values related to a particular thing in one go. Exceptions are missing too, and you have to rely on ambiguous return values.
This standards-compliant wrapper addresses all of the above. It is a true PSR-16 cache, which uses WordPress transients as storage. Exceptions are raised, interfaces implemented, and true false-negative detection is in place. Each instance of the cache pool is logically independent from other instances, provided that it is given a unique name. The application is once again in control, and modules that use cache can become platform agnostic.
Compatibility
CachePoolandCachePoolFactoryoffer best-practices error handling, throwing meaningful exceptions when something goes wrong. This violates PSR-16, but allows you to know what is failing.SilentPoolandSilentPoolFactoryoffer PSR-16 compatibility at the cost of error handling, hiding exceptions, and returning standards-compatible values. This complies with PSR-16, but at the cost of clarity and verbosity.
Usage
Limitations
Key Length
Due to the way the underlying backend (the WordPress transients via options) works, the combined length of the
pool name and cache key MUST NOT exceed a 171 char limit. This is because (at least in WP 5.0+)
the length of the option_name field of the options table is 191 chars, and transients require the longest
prefix of _transient_timeout_ to the option name, which together with the 1-char separator is 20 chars. Using
anything greater than this length will result in potentially devastating behaviour described in Trac #15058.
In any case, the general recommendation is that consumers SHOULD NOT use cache keys longer than 64 chars, as this is the minimal length required for support by the PSR-16 spec. Using anything longer than that will cause consumers to become dependent on implementation detail, which breaks interoperability. Given that, the cache pool name SHOULD NOT exceed 107 chars.
Value Length
The storage backend (WP options) declares the corresponding field to be of type LONGTEXT, which
allows up to 4 GB (232) of data. This is therefore the limit on cache values.
