Warm Regards,
Sameer S.
Kekade.
-----Original Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew
Scott
Sent: Tuesday, 13 July 2004 12:29 PM
To: CFAussie
Mailing List
Subject: [cfaussie] RE: Persisting some session variables
on session timeout
---Sameer,Let me get this right, because we do the same thing now with our clients.Do you have a separate database for each site, or is it a single login across sites?If it is single login cookie with domains is the way to go, if it is separate database session will work for each site. Although I personally hate session variables.However if they are not logged in, you will not be able to skin.
Regards
Andrew Scott
Technical Consultant
NuSphere Pty Ltd
Level 2/33 Bank Street
South Melbourne, Victoria, 3205
Phone: 03 9686 0485 - Fax: 03 9699 7976
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sameer Kekade
Sent: Tuesday, 13 July 2004 12:21 PM
To: CFAussie Mailing List
Subject: [cfaussie] RE: Persisting some session variables on session timeout---yes.. we do have a database with the users details ..
but the entry points may be different and so is the skin..
for example
www.site1.com.au shows one skin
www.site2.com.au shows another
we might have one user using either of these websites by itself or simultaneously in different browser sessions
Hence on session timeout, I'm unsure what skin is to be displayed.
I tried few approaches like cfcookie that has values session_id & skin
or an array of client variables that has session_id and skin used for each browser each session.
Not sure if that's the right way
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
