-
-
Notifications
You must be signed in to change notification settings - Fork 6
Distinct Logic Authority
Each operational state of an application should have one clear entry point. In web applications, the URL is the natural place for that to begin.
That idea becomes much easier to follow in hypermedia applications, where HTML over HTTP is still the main model and each page state is represented by an actual requestable location.
Distinct logic authority improves traceability because it is immediately obvious where the request begins. If a button does not work, we can usually:
- identify the page URL
- find the page logic
- find the matching action or
gohandler - inspect redirects or response headers if the flow changes
That avoids duplicated behaviour being spread across several hidden entry points.
WebEngine reinforces this idea through file-based routing and thin page logic. A URL maps to a clear page file, and actions map to clear do_* functions.
The framework also leaves useful traces in response headers during development, such as where redirects came from and which logic hooks executed, which makes the request path easier to inspect.
Next, read SPA vs MPA.
- File-based routing
- Page views
- Page logic
- Dynamic URIs
- Headers and footers
- Custom HTML components
- Page partials
- Binding data to the DOM
- DOM manipulation
- Hello You tutorial
- Todo list tutorial
- Address book tutorial WIP
- Blueprints
- Application architecture
- Coding styleguide WIP
- PHP environment setup WIP
- Web servers WIP
- Background cron tasks
- Database setup WIP
- Client-side compilation WIP
- Testing WebEngine applications WIP
- Production checklist WIP
- Security WIP