Developer’s Guide
This documentation is a work in progress. It was originally written for a previous, commercially-available version of Traffic Server that supported different operating systems and more functions than the current version. As a result, some of the sections may refer to functionality that no longer exists.
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.
- Introduction
- Release Process
- 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
- 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 Reference
- Continuous Integration
- Documentation
- Host Resolution Proposal
- An Overview Client Sessions and Transactions
- Core Architecture
- Design Documents
- Layout
- Testing Traffic Server
- JSONRPC