I am guessing this talk of a central server is a central domain like erenetwork.com which would hold all the session data in the database. Whenever someone accesse say domainA.com it would redirect to erenetwork.com, get the session data then redirect to domainA. with the session id in the header or something is that correct?
On 3/26/07, Michael B Allen <[EMAIL PROTECTED]> wrote:
On Mon, 26 Mar 2007 22:03:07 -0400 "Joseph Crawford" <[EMAIL PROTECTED]> wrote: > Mike, > > If i cam correct you cannot use cookies in this manner because > domainB.comcould not read a cookie set by > domainA.com Right but I'm not suggesting that you put a logon session key in the cookie, just something to represent their identity. So the first time someone visited a site they would have to login regardless. But that's only the first time. Once the cookie saved their identity (which is fixed in time) the server would know who who the client is and could consult the "central server" to retrieve the user's session state. Mike -- Michael B Allen PHP Active Directory Kerberos SSO http://www.ioplex.com/
-- Joseph Crawford Jr. Zend Certified Engineer Codebowl Solutions, Inc. http://www.codebowl.com/ Blog: http://www.josephcrawford.com/ 1-802-671-2021 [EMAIL PROTECTED]
_______________________________________________ New York PHP Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
