1. Get Started with the Framework
2. Overview of Opendelight Architecture
3. Opendelight Objects, Arrays and Libraries
4. Opendelight Application Database Structure
5. Opendelight Application File Structure
6. Controller in Opendelight
7. Event in Opendelight
8. Model in Opendelight
9. View in Opendelight
10. Users and Roles in Opendelight
11. Overview of Opendelight IDE
12. Opendelight Coding Standards and Conventions
13. Installation and Upgrades of Opendelight
Controller in Opendelight
A *Controller* is a PHP file that takes the HTTP request and manages the execution path of the application (instance of the application) at the server-side. An application can have more than one controller file when required. A Controller file can define *public URLs* or *private URLs* (i.e., password-protected URLs) or even *mixed URLs* (where user session is optional) as the situations demand. However, a Controller file cannot have both public and private URLs, and you need separate Controller files for this.
A Controller file is defined and edited by the Opendelight IDE and requires the developer to specify the controller file name. The Controller file name can be prepended by the path from the root of the application folder if it is located inside an inner directory, but never include any slash in the beginning. For example
- The controller name is `mycontroller.php` if it is located in the application root
To continue reading "Controller in Opendelight", login now.
This page has been protected for subscriber only and it is free to subscribe.