Hmmm...
Some thoughts:
1) You could maintain multiple independent sessions logically by simply
establishing some naming convention of session key values in the one
session. All admin session keys are session[:admin_xxx] and all
"regular" session keys are session[:regular_xxx]. You could enforce
this fairly easily with a couple of wrapper functions and the discipline
to never access the session directly.
2) You could also embed one "session" inside the standard session object
by simply establishing a session key of "inner_session" (or
"admin_session" or whatever). This would likely require you to decide
which session the top-level keys represented and which the "inner" key
was responsible for. Same as #1, just not flat.
3) You could maintain a Session AR object independent of the "session"
object. Similarly, if you were using cookie based sessions, you could
always just maintain a completely separate cookie that you manage by hand.
4) You could always force a logout from one auth. system when the user
logs in to the other, assuming that both logins don't need to be active
at the same time.
W
On 10/6/10 10:26 AM, swartz wrote:
Hi Wes,
Yeap pretty much.
On Oct 5, 6:36 pm, Wes Gamble<we...@att.net> wrote:
So you need to maintain two distinct sessions from one browser? Is
that right?
W
On 10/5/10 6:22 PM, swartz wrote:
I have a 0.9.1-based radiant install that uses a custom end-user auth-
system. It uses authlogic and based primarily on examples from reader
and members extension.
I've switched from the default cookie session store
to :active_record_store for storing session information.
And I've also ran into a problem. Both radiant admin and my custom
auth system end up sharing session. Specifically, if I have a user
that logs into Radiant admin AND into the custom auth system to view
content, the session gets messy. Thing sometimes get REALLY messy
(wrong redirects, etc).
Any way to separate session storage into different table instead of
one common one?
