The names the OTP files take beside the configured OTP_REQUESTS_PATH.
Every request is its own file, `..json`, and its answer is
`..answer.json`, where the stem is the configured name without
`.json` and the id is a lower-case UUID. The configured name itself is the
combined file an older release wrote. A staged copy of any of these adds a
`..tmp` tail, the grammar every store stages under.
Parsing is as strict as naming: a name is a request's or an answer's only
if the id in it is a UUID, so no name built here can leave the directory and
no stranger's file is mistaken for one of these.
The names the OTP files take beside the configured
OTP_REQUESTS_PATH.Every request is its own file, `..json`, and its answer is
`..answer.json`, where the stem is the configured name without
`.json` and the id is a lower-case UUID. The configured name itself is the
combined file an older release wrote. A staged copy of any of these adds a
`..tmp` tail, the grammar every store stages under.
Parsing is as strict as naming: a name is a request's or an answer's only if the id in it is a UUID, so no name built here can leave the directory and no stranger's file is mistaken for one of these.