G'day Sluggers,
I've inherited a LAMP stack which uses the php session stuff to maintain a session with an authenticated user. A cookie gets sent
to the user and upon it's return PHP retrieves the "session" from a file in the "sessions" folder.
I would like to change the setup such that the site could be hosted on multiple web servers. The PHP sessions would then be badly
broken because the user could potentially be directed to the "other" server depending on what load balancing solution was used,
which would not have the matching "sessions" file. I do not want to use a solution that has the load balancer direct the user back
to the same server because a lot of the reason for load balancing is for redundancy or to be able to take a server off-line to
service / upgrade it etc.
The multiple web servers would initially share a a single back-end DBMS server, but in future would have their own dedicated
back-end DBMS, with the DBMS servers using replication to keep in sync.
I am looking for documentation, user-groups, articles, advice etc that describe the pros/cons of different solutions to meeting
this requirement and thought I might ask the collective wisdom of Slug.
TIA
Pete
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
