About
These pages explain Drash—why it was designed the way it was, how its parts fit together, and what changes from one version to the next.
Concepts
What Drash is, why it is shaped the way it is, and how it works beneath the surface. Read on if you want to understand the underpinnings of Drash.
| Page | Covers |
|---|---|
| Framework | The three-layer split, and why imports only flow one direction |
| HTTP Application | What Application assembles, and what it expects from you |
| Resources | Why Drash routes with classes instead of app.get() |
| Native vs. Polyfill | The two entry points, and which one your runtime needs |
| Chains | The chain of responsibility every request travels |
| Builders | The builder pattern used to assemble applications and resource groups |
Releases
Notes for every published version, newest first — what changed, what broke, and what to do about it. See All Releases.
Last updated on