发布于 2015-08-21 15:27:23 | 362 次阅读 | 评论: 0 | 来源: 网络整理
The PhalconSession provides object-oriented wrappers to access session data.
Reasons to use this component instead of raw-sessions:
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 PhalconSessionAdapterFiles as Session;
// Start the session the first time when some component request the session service
$di->setShared('session', function () {
$session = new Session();
$session->start();
return $session;
});
From a controller, a view or any other component that extends PhalconDIInjectable you can access the session service and store items and retrieve them in the following way:
<?php
use PhalconMvcController;
class UserController extends Controller
{
public function indexAction()
{
// Set a session variable
$this->session->set("user-name", "Michael");
}
public function welcomeAction()
{
// Check if the variable is defined
if ($this->session->has("user-name")) {
// Retrieve its value
$name = $this->session->get("user-name");
}
}
}
It’s also possible remove specific variables or destroy the whole session:
<?php
use PhalconMvcController;
class UserController extends Controller
{
public function removeAction()
{
// Remove a session variable
$this->session->remove("user-name");
}
public function logoutAction()
{
// Destroy the whole session
$this->session->destroy();
}
}
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 PhalconSessionAdapterFiles as Session;
// Isolating the session data
$di->set('session', function () {
// All variables created will prefixed with "my-app-1"
$session = new Session(
array(
'uniqueId' => 'my-app-1'
)
);
$session->start();
return $session;
});
Adding a unique ID is not necessary.
PhalconSessionBag 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 PhalconSessionBag as SessionBag;
$user = new SessionBag('user');
$user->setDI($di);
$user->name = "Kimbra Johnson";
$user->age = 22;
Controller, components and classes that extends PhalconDIInjectable may inject a PhalconSessionBag. 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 PhalconMvcController;
class UserController extends Controller
{
public function indexAction()
{
// Create a persistent variable "name"
$this->persistent->name = "Laura";
}
public function welcomeAction()
{
if (isset($this->persistent->name)) {
echo "Welcome, ", $this->persistent->name;
}
}
}
In a component:
<?php
use PhalconMvcController;
class Security extends Component
{
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.
The PhalconSessionAdapterInterface 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