Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
kmvc is a micro MVC framework that have a convention over confiugration approach which will save you from registering urls for different actions you want to create in Drupal and it will provide you an object oriented approach to handle your module.
It attaches itself to the menu_hook and create custom on the fly routes for the controller classes you have defined in your library.
It's completely Object Oriented and provides a very simple structure for developers new to the Drupal. You have to define some small configurations in your .module file which are pretty easy and you will be ready to go in no time.
It does not override the current routing of Drupal but it comes around right before a 404.
Usage of Controllers and Actions are similar to the Zend Framework, where each controller should be defined with a Controller suffix and each action should have an Action suffix. These classes should be managed in an app and controllers folders. It has a support for modules too where controllers can be grouped into modules.
The Mixed Session module enables mixed HTTP(S) sessions for a site, securely and without loss of session data. The phrase "mixed sessions" refers to providing, with respect to a user visiting a site, some content over an insecure (HTTP) connection and other content over a secure (HTTPS) connection. For example, a shopping site may prefer to display product content in insecure mode (HTTP) while being able to protect sensitive content (e.g credit card details and authenticated user account information) using secure mode (HTTPS). The use of mixed sessions adds complications such as preserving session data (e.g. a cart ID) across session mode and protecting against session hijacking (with tools such as Firesheep). This module addresses both concerns.
The Mixed Session module protects against session hijacking by regenerating session IDs on step up and step down (i.e. switching between HTTP and HTTPS), providing a configuration switch to stay secure once having entered secure mode, and exposing more built-in, configurable redirect rules. This module also declares two API hooks through which a developer can incorporate more complex redirect rules. Protection applies to anonymous and authenticated users.