Sections

Session Component


Storing data in the Session

The session component provides object-oriented wrappers to access session data.

Reasons to use this component instead of raw-sessions:

  • Aislar fácilmente datos de sesión en las aplicaciones en el mismo dominio
  • Interceptar donde se establecen los datos de la sesión en su aplicación
  • Cambiar el adaptador de la sesión según las necesidades de aplicación

Starting the Session

Some applications are session-intensive, almost any action that performs requires access to session data. There are others who access session data casually. Thanks to the service container, we can ensure that the session is accessed only when it’s clearly needed:

<?php

use Phalcon\Session\Adapter\Files as Session;

// Iniciar sesión por primera vez cuando algún componente solicite el servicio de session
$di->setShared(
    'session',
    function () {
        $session = new Session();

        $session->start();

        return $session;
    }
);

Factory

Loads Session Adapter class using adapter option

<?php

use Phalcon\Session\Factory;

$options = [
    'uniqueId'   => 'my-private-app',
    'host'       => '127.0.0.1',
    'port'       => 11211,
    'persistent' => true,
    'lifetime'   => 3600,
    'prefix'     => 'my_',
    'adapter'    => 'memcache',
];

$session = Factory::load($options);
$session->start();

Storing/Retrieving data in Session

From a controller, a view or any other component that extends Phalcon\Di\Injectable you can access the session service and store items and retrieve them in the following way:

<?php

use Phalcon\Mvc\Controller;

class UserController extends Controller
{
    public function indexAction()
    {
        // Definir una variable en sesión
        $this->session->set('user-name', 'Michael');
    }

    public function welcomeAction()
    {
        // Comprobar si una variable esta definida
        if ($this->session->has('user-name')) {
            // Obtener dicho valor
            $name = $this->session->get('user-name');
        }
    }

}

Removing/Destroying Sessions

It’s also possible remove specific variables or destroy the whole session:

<?php

use Phalcon\Mvc\Controller;

class UserController extends Controller
{
    public function removeAction()
    {
        // Eliminar una variable
        $this->session->remove('user-name');
    }

    public function logoutAction()
    {
        // Destruir toda la sesión
        $this->session->destroy();
    }
}

Isolating Session Data between Applications

Sometimes a user can use the same application twice, on the same server, in the same session. Surely, if we use variables in session, we want that every application have separate session data (even though the same code and same variable names). To solve this, you can add a prefix for every session variable created in a certain application:

<?php

use Phalcon\Session\Adapter\Files as Session;

// Aislamos los datos de la sesión
$di->set(
    'session',
    function () {
        // Todas las variables de la sesión tendrán el prefijo 'my-app-1'
        $session = new Session(
            [
                'uniqueId' => 'my-app-1',
            ]
        );

        $session->start();

        return $session;
    }
);

Adding a unique ID is not necessary.

Session Bags

Phalcon\Session\Bag is a component that helps separating session data into namespaces. Working by this way you can easily create groups of session variables into the application. By only setting the variables in the bag, it’s automatically stored in session:

<?php

use Phalcon\Session\Bag as SessionBag;

$user = new SessionBag('user');

$user->setDI($di);

$user->name = 'Kimbra Johnson';
$user->age  = 22;

Persistent Data in Components

Controller, components and classes that extends Phalcon\Di\Injectable may inject a Phalcon\Session\Bag. This class isolates variables for every class. Thanks to this you can persist data between requests in every class in an independent way.

<?php

use Phalcon\Mvc\Controller;

class UserController extends Controller
{
    public function indexAction()
    {
        // Crear una variable persistente 'name'
        $this->persistent->name = 'Laura';
    }

    public function welcomeAction()
    {
        if (isset($this->persistent->name)) {
            echo 'Bienvenido, ', $this->persistent->name;
        }
    }
}

In a component:

<?php

use Phalcon\Di\Injectable;

class Security extends Injectable
{
    public function auth()
    {
        // Create a persistent variable 'name'
        $this->persistent->name = 'Laura';
    }

    public function getAuthName()
    {
        return $this->persistent->name;
    }
}

The data added to the session ($this->session) are available throughout the application, while persistent ($this->persistent) can only be accessed in the scope of the current class.

Implementando sus propios adaptadores

The Phalcon\Session\AdapterInterface interface must be implemented in order to create your own session adapters or extend the existing ones.

There are more adapters available for this components in the Phalcon Incubator