Developer's Guide
このドキュメントは執筆中です。このドキュメントはもともと現在の Traffic Server よりも多くの機能をもち異なるオペレーティングシステムをサポートとしていた、以前の商用の Traffic Server のために書かれたものです。そのため、いくつかの章はもはや存在しない機能について言及しているかもしれません。
If you find any such issues, you may want to submit a bug or a patch. We also have a Wiki page explaining how to create useful bug reports. We encourage everyone to file tickets, early and often. Looking for existing, duplicate bugs is encouraged, but not required.
- 導入
- リリースプロセス
- Contributing to Traffic Server
- Debugging and Analysis
- Threads and Event Processing
- Cache Architecture
- Logging Architecture
- Internal libraries
- Plugin Development
- Cripts
- Configuration Variable Implementation
- Configuration Reload Framework
- Overview
- Registration API
- ConfigContext API
- Terminal State Rule
- ConfigSource
- ConfigType
- Adding a New Config Module
- Composite Configs
- Startup vs. Reload
- Plugin Configuration Reload
- Thread Model
- Naming Conventions
- What NOT to Register
- Logging Best Practices
- Unified Diagnostic Macros (
CfgLoad*) - Severity-Aware Task Logs
- Reload Summary in
diags.log - Testing
- Configuration Records
- API リファレンス
- Continuous Integration
- Documentation
- Host Resolution Proposal
- An Overview Client Sessions and Transactions
- Core Architecture
- Design Documents
- Layout
- Testing Traffic Server
- JSONRPC