> If you are sending a user to a single specific server, then why bother > with the load balancer? I would just do the simplest path, which is > send them a unique URL pointing to "their" server. For example, login > to a main page, do your database lookup there and present them with a > link to continue. The link will contain a url to "their" server (eg: > host9.x.com).
Thanks for your suggestion. I guess I am going with something similar (in lines of Ezra's suggestion). At first the user gets forwarded to any of the servers which figures out which server he really belongs to. It then sets a cookie for the load balancer for future forwarding to the right server. It also serves the main page. By doing it this way, the user notices nothing explicitly about the redirection. He may notice the slower response time for just the first request. Thanks, Ram -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
