ansaurus

Question

Zend framework - Where to Initialize session when the router needs access to it

Answer 1

A:

I would move the session initialization and db connection to the bootstrapping.
If you can't connect to your db during bootstrapp this should count as low-level error. It is not excepted to happen in production.
Simply wrap your bootstrapping process into a try catch block so you can output an error page.

// in your index.php
try {
    $application = new Zend_Application(
        APPLICATION_ENV,
        APPLICATION_PATH . '/configs/application.ini'
    );

    $application->bootstrap()
                ->run();

} catch (Exception $e) {
    header('Content-type: text/html; charset=utf-8');
    header('HTTP/1.1 503 Service Unavailable');
    header("Retry-After: 3600");
    // Output some error page.
    echo "<html><head><title>System Error</title></head><body>...</bod></html>";
?>

Benjamin Cremer 2010-07-26 07:41:33

Thanks. I also think that db and session should belong to bootstrapping but then sending headers and echoing in the bootstrap file (or any included file) is not the 'Zend way' to display an error page. And we don't have (direct) access to the request to be able to make a redirect. I have an error controller with logging, email sent and a nice view which is called there, i just wanted to make it the 'Zend way'. I think this is a chicken and egg problem.

Mr X Colombia 2010-07-27 12:18:17

I use the error controller, loggin etc. too. But some errors you can't catch and handle gracefully in the "Zend Way" cause they appear to early. Think about if your application.ini is not readable. What does your application do now? So a low-level handling is required anyway.

Benjamin Cremer 2010-07-27 13:31:12

ansaurus

tags:

views:

answers:

Zend framework - Where to Initialize session when the router needs access to it

related questions