-
Notifications
You must be signed in to change notification settings - Fork 146
Handlers
Controller manages the flow of all REST full services and any other controller configured in the application. It is also responsible for managing the mappings of URL and URL extensions. A controller simply put maps a URL to an actual C++ class method.
Manages authentication/security support. Provides in-built authentication support via file/interfaces. Authentication interfaces can be implemented or the methods required can be implemented to provide custom authentication support.
This handler is responsible for managing Templates, Dynamic C++ pages, Ajax interfaces, Fviews and DynamicView's.
Is responsible for identifying and executing an appropriate SOAP method based on the URL and the mapped class
Any request can be intercepted by the framework to provide checks on pre/post conditionals and execute some predefined logic based on the request life-cycle. Filters provide their functionality with the help of 3 events the in, out and the handle modes.
Fviews are intelligent views provided by the ffead-cpp framework. In an fview (ffead-view) an event and the back-end API logic behind those events are very closely knit together. When you write a C++ class for your Fview all your your C++ class methods are exposed as javascript methods in your HTML Fview file.
Form handler is responsible for mapping a POCO class or a simple C++ bean class to an HTML form page whenever the form is submitted to the appropriate FORM handler in ffead-cpp. The handler is responsible for connecting the form data to the class object and process the form controller implementation method.
Provides a CGI styled handler to execute scripts for any interpreted PL (programming language) like Ruby, Lua, Python, PHP, nodejs etc.
Configuration management handler, responsible for reading all configuration files and markers, generate intermediate code and setup configuration cache for handling all requests.