Re: [phplib] Remote session/authentication From: Sam C. Nicholson !! (scion <email protected>)
Date: 07/31/01

>>yes : but how could you do that where the 2 (or n) servers cannot share
>>the file directly ?

You can't use XXX if the client (the PHP webserver) doesn't (or isn't allowed to)
participate in a uniformly shared XXX service.

If NFS isn't allowed to all of your client servers, then you can't use NFS.

No matter which data sharing method you use, you must allow remote access to
the data. If this is a problem, then you must evaluate each method to find
the method which meets the most requirements, and then patch/politic around
the rest.

For shared auth, when one system can serve as a login webserver, I then
export the shared filesystem read only via NFS, accessing the master file
from the PHP via the local filesystem.

My programming partner is very keen on Kerberos, as it allows any client to
initiate the authentication.

In all of these cases one must plan for network partitions. They will happen;
even on a LAN, even on a shared resource system (though for very short times.)

I generally deal with a partition from the auth source by caching a local copy
at each access time. Then if a user returns, yet I cannot see the master data
source, I will allow read-only access. This splits the middle between absolute
auth and convenience.

-sam 

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>