-
Notifications
You must be signed in to change notification settings - Fork 20
Routing
The routers along the lines suggested by Niels and Hannes (with possible additions from the Framework’s router) are used as a base. The menu system is used to generate custom route patterns for specific sites. The route must still run through JComponentHelper. For REST we can support “best practice” URLs using the same router.
The approach provides ability for autogenerating route patterns, but allow for customization. Best practice RESTful URLs come out of the box. A router.php will no longer be needed in components.
As there are going to be multiple MVC systems used within 3rd party components the routing must be independent of the MVC layer. JComponentHelper is therefore used to “dispatch” components in the CMS and therefore all routing should call the component helper.
This is a collection of statements and comments on Glip regarding the router.
@2015-09-05 05:05
Introduction
Development
Architecture
- Universal Content Model (UCM)
- Command Query Responsibility Segregation (CQRS)
- Database Abstraction Layer (DBAL)
- Dependency Injection (DI)
- Event Sourcing (ES)
- Filesystem Abstaction Layer
- Installer
- Data Definitions (JForms)
- Model-View-Controller (MVC)
- Orthogonal Component Structure (OCS)
- Routing
Features
Appendix