Mladen Turk wrote:
Ok, just wanted to clear if we are going to make another compromise :), since sticky sessions are tightly coupled with the load balancer itself and the way it decides the client route.
In theory sticky sessions shouldn't be tightly coupled like this - it should be a case of "plan a) stick to the same server, else revert to plan b)".
In this case plan B could be simple DNS round robin, or it could be a load balancer, in other words another module entirely.
This raises a question - what order do the modules run in? In theory the sticky module should run last, in other words a load balancer (or DNS round robin, or whatever) orders the IPs based on some criteria (load, or round robin, or whatever), and then the sticky module takes the sticky server identified by the cookie/parameter and moves that sticky IP on top of the list.
I suppose in this case the load balancer would run HOOK_MIDDLE, and sticky would run HOOK_LAST.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
