Filip Hanik wrote: > > The current jvmRoute addition to JSESSIONID is not really > needed, since it doesn't add that much of a benefit over the > two options above. So right then and there, there is one less > thing to configure. >
Ok, If we'll make a lb for a mod_proxy, then at least it will need a balance load factor, not just sticky sessions and simple round robin. Also the JSESSIONID then does not to be harcoded, but rather configurable. MT.
smime.p7s
Description: S/MIME cryptographic signature
