That is why I was thinking of having it look for the original cookie
set on login, then connect to the root site's DB, grab the needed row
from the Users table for that specific user, then switch back to it's
own DB, and set the needed session data there and take the ID from the
previously grabbed row, and look up in the app's own Users table for
that specific ID, which would give it any extra information it needs,
such as credits, post counts, nicknames, etc... I really wish I could
post a full workup on what I am doing, but my partners would kill me
as they want everything kept hush-hush and discussed in as vauge terms
as possible, so the idea doesn't get stolen before we debut it...
Doesn't quite make it easy to ask for help when experimenting with a
new framework at the same time... *C*
On Jun 24, 2:40 pm, francky06l <[EMAIL PROTECTED]> wrote:
> Basically you want to share the session.
> I have tried something like this (maybe a bit unsecured thought), in
> your link you can pass an argument 'sessid:xxxxxxx' ..You can get the
> value using Session->id();
>
> On the different application, in beforeFilter, you can do :
>
> if(isset($this->params['named']['sessid']))
> {
> // we restore the session for the underwriter uploading
> $this->Session->id($this->params['named']['sessid']);
> $this->Session->activate('/');
>
> }
>
> As I said might a a security issue, you could also check by storing
> session in DB and share the DB accross applications
> hth
>
> On Jun 24, 6:53 pm, Infinite Knight <[EMAIL PROTECTED]> wrote:
>
> > Just curious... This may have been asked before but I missed it in my
> > searches... I am designing a multi-site app, where each sub-site is a
> > seperate app, but yet part of the larger core... The following layout
> > is what I am after, any pointers to such would be helpful...
>
> >http://www.domain.com(Allusers start / login here)
>
> > Once logged in, a user will see a menu show up on the right or left,
> > depending on the theme they have set in their preferences, that will
> > allow them to access the sub-apps, such as:
>
> >http://sub1.domain.comhttp://sub2.domain.comhttp://sub3.domain.com
> > etc...
>
> > If the user tries to directly access one of the sub-apps, the system
> > should re-route them back tohttp://www.domain.comtologin...
>
> > While at first look this should be simple, (and is, if I were using
> > one single DB), but since I am using a DB per sub-app, so I can take
> > entire sites / DBs offline periodically for optimization, maintance,
> > etc, not to mention keep from having a gigabyte sized DB to work on, I
> > need a way to reference data from the core site's DB to user data in
> > the sub-app's DB...
>
> > Right now, I have my cake libraries installed under /home/user/cake,
> > and each sub-app is installed as:
> > /home/user/public_html/sub1/app
> > /home/user/public_html/sub2/app
> > /home/user/public_html/sub3/app
> > etc...
>
> > The root site (http://www.domain.com) is installed as: /home/user/
> > public_html/app
>
> > That part I have running right... So now I just need to share the
> > login status... Since all sites use the same basic theme / user
> > preferences data, what I am thinking is having Cake reference the root
> > site's DB to get the user preference data from the Users table, then
> > switching to it's own DB and using the user's ID from the gathered
> > preference data to reference a local user table that contains the
> > extra items specific to that site...
>
> > Or is there a better way?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" 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
-~----------~----~----~----~------~----~------~--~---
