> I am trying to configure pound to help me first determine a what backend > to send the request to, and then to maintain affinity for that backend.
> Is there a way to configure pound to perform the HeadRequire once, and > then use session tracking to keep the user at a backend? Nobody? Anybody with any alternatives or ideas about how they might pull this off? My other line of thinking revolves around using Apache + mod_proxy (et. al.) to proxy a request back to one 4 pound listeners that each represent one of our notes clusters. Once the request is at the proper pound listener, session affinity is handled using the LtpaToken cookie described above. I've got proof of concept somewhat working using this method, but I'm not sure if it is the appropriate path to go down. I'd be happy to hear from anybody who has an opinion or advice. Any response appreciated, Justin -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
