On 4/11/2011 1:04 PM, Mohit Anchlia wrote:
Yes that's correct. After giving it a thought and seeing how complicated this approach was becoming, we have decided to change our API calls to include user identifier in query string. We use LTM F5 and we will persist user info at F5 LTM with expiry set to 1 hr.
If you have an LTM, you can just set its internal cookie persistence mechanism to tie a session to a particular server in the pool without doing anything different in the application. The initial connection will be balanced however the pool is configured. But that's only within the pool at a single data center (the L in LTM meaning local...) where the servers probably all have access to the same memcache service.
-- Les Mikesell lesmikes...@gmail.com
