Most of our websites use sessions to store a variable like loggedInUserID to track who is logged in. To handle the load from advertising campaigns, I've setup two computers with Apache and Webkit running on each. I then use round robin DNS so hopefully an individual user will go to the same web server and get the same session and remain logged on. This works pretty well but we get several complaints a day from people that can't stay logged on which I assume means they are going to the other web server and getting a different session.
I'm thinking maybe I should stop using sessions and just store some form of the UserID in a cookie which should work no matter which server they go to for each request. It would really be nice if I could run Apache on one machine, and run Webkit on the other but I don't think it would improve performance much and maybe even make it worse since Apache would have to talk to WebKit across the LAN. Does anyone have any advice? Does splitting the web server and application server onto two machines have much impact? Thanks, Jeff _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
