RFC: 6.x - Change the default engine for `_cake_translations_` to `PhpEngine`.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 387
- Forks
- 392
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
The TranslationsRegistry caches the full Translator instances. Switching from the current FileEngine which uses serialize()/unserialize() to PhpEngine which generates PHP code (which can be opcached) would give better performance gain.
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 by tracing how TranslationsRegistry caches Translator instances and where the default cake_translations engine is selected. Compare the current FileEngine serialization path with PhpEngine's generated PHP path; done means the default is changed to PhpEngine and the translation cache behavior and performance rationale are validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- internationalization, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100