[thesite] UEUE v.0.2 Update

[.jeff]

dan,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Daniel J. Cody
>
> i'm sorry for not putting that in the correct context.
> i should have said, 'theres nothing except that one
> page that credentials are required for'. making people
> type in two pieces of information shouldn't be a
> showstopper for UEUE.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

i agree.  for now i think the big showstopper is whether or not the ueue
cookie can be read from the m.e.o. accounts.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> if we decide to add new services to m.e.o. then we
> could address it at that time again, *if and when that
> happens*.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

again, i agree.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> unified logins are a big problem for evolt. we need to
> look past the 'what if' and 'if we ever' scenerios.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

once again, i agree.  it's important to try take a look at all the
implications before implementation though.

if unified login is all this is for (not unified session state), then i've
got a question for you.  why don't we simply query the users table based on
the user's persistent login cookie?  that would sure save all the hassles of
the various browser bugs regarding redirects, users that disable cookies,
building something complex and complicated like ueue, etc.

thanks,

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/