memcached / memcached/memcached.github.io
missing proxy docs
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 4
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
importing some TODO's/missing sections that are getting trimmed via a PR:
```
- `resp:code()`: the response code. Common codes are:
- `mcp.MCMC_CODE_OK`
- `mcp.MCMC_CODE_STORED`
- `mcp.MCMC_CODE_EXISTS`
- `mcp.MCMC_CODE_MISS`
- TODO: document the rest.
```
from examples page:
```
### Cache Layering Cons
- Needs more complex application clients.
- Configuration of pools needs to be managed in two places (application
clients, memcached proxies)
---
# Use Case Examples
## Simplifying and Unifying Cache Clients
## Distributing data by usage
## Best effort data redundancy
## Transparent upgrades
## Transparent pool resizing
## Protocol translation
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the response-code section and the examples page referenced in the issue, then inspect the surrounding proxy documentation for context. Identify which response codes and use-case sections are still missing, and confirm that the completed pages no longer contain the listed TODOs or empty headings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- memcached
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100