Skip to content

Commit ef216f1

Browse files
committed
Clarified cache key length recommendation
1 parent ebf8092 commit ef216f1

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -74,10 +74,10 @@ the [length of the `option_name` field of the `options` table is 191 chars][1],
7474
prefix of `_transient_timeout_` to the option name, which together with the 1-char separator is 20 chars. Using
7575
anything greater than this length will result in potentially devastating behaviour described in [Trac #15058][].
7676

77-
In any case, the general recommendation is to not use cache keys longer than 64 chars, as this is the minimal
78-
length required for support by the PSR-16 spec. Using anything longer than that will cause consumers to become
79-
dependent on implementation detail, which breaks interoperability. Given that, **the cache pool name SHOULD NOT
80-
exceed 107 chars**.
77+
In any case, the general recommendation is that **consumers SHOULD NOT use cache keys longer than 64 chars**,
78+
as this is the minimal length required for support by the PSR-16 spec. Using anything longer than that will
79+
cause consumers to become dependent on implementation detail, which breaks interoperability.
80+
Given that, **the cache pool name SHOULD NOT exceed 107 chars**.
8181

8282
#### Value Length
8383
The storage backend (WP options) [declares][2] the corresponding field to be of type [`LONGTEXT`][], which

0 commit comments

Comments
 (0)