Use database sessions, that's what all the cool kids are doing.
// app/config/core.php:
define('CAKE_SESSION_SAVE', 'database');
On Feb 7, 12:35 pm, "John David Anderson (_psychic_)"
<[EMAIL PROTECTED]> wrote:
> On Feb 7, 2007, at 10:30 AM, Chris Hartjes wrote:
>
>
>
>
>
> > On 2/7/07, codecowboy <[EMAIL PROTECTED]> wrote:
>
> >> My company Lifeagora has launched... Finally!!! (applause) We are
> >> in the process of setting up a scalable architecture which would of
> >> course allow us to use a load balancer to divi up requests between
> >> several apache servers. This not my cup of tea, so this may come off
> >> as a newbie question. Will I need to change Cake's Session Component
> >> so that is works when multiple servers are creating sessions at the
> >> same time? Or, is this something that I will fix inside of apache?
>
> > Having been through this on a non-CakePHP app, I offer the
> > following advice:
>
> > 1) you will need a custom session handler so that requests on multiple
> > servers will have unique ID's if your load balancer moves someone from
> > one server to another
>
> Cake's database sessions is a custom handler.
>
> By pointing all your applications to look at a single database table
> for session info, you remove the problems created by clustering.
>
> > 2) you will likely have to change Cake's session component in some way
> > to get it to use a custom session handler instead of the stock one.
>
> Not if you use database sessions, or configure your PHP session files
> to reside on a share that can be accessed by all the nodes in the
> cluster.
>
> -- John
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
