I wanted to do the exact same thing but ending up just doing something similar but not as good basing the backend on the calling ip. <br><br>The problem with pound is that all session tracking is per service, and there is no global sessions.<br>
<br>Sorry, no better help from me :(<br><br><div class="gmail_quote">On Tue, Jan 27, 2009 at 18:15,  <span dir="ltr">&lt;<a href="mailto:justin.kinney@academy.com">justin.kinney@academy.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">&gt; I am trying to configure pound to help me first determine a what backend<br>
&gt; to send the request to, and then to maintain affinity for that backend.<br>
<br>
</div><div class="Ih2E3d">&gt; Is there a way to configure pound to perform the HeadRequire once, and<br>
&gt; then use session tracking to keep the user at a backend?<br>
<br>
</div>Nobody? &nbsp;Anybody with any alternatives or ideas about how they might pull<br>
this off?<br>
<br>
My other line of thinking revolves around using Apache + mod_proxy (et.<br>
al.) to proxy a request back to one 4 pound listeners that each represent<br>
one of our notes clusters. &nbsp;Once the request is at the proper pound<br>
listener, session affinity is handled using the LtpaToken cookie described<br>
above. &nbsp;I&#39;ve got proof of concept somewhat working using this method, but<br>
I&#39;m not sure if it is the appropriate path to go down. &nbsp;I&#39;d be happy to<br>
hear from anybody who has an opinion or advice.<br>
<br>
Any response appreciated,<br>
Justin<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
--<br>
To unsubscribe send an email with subject unsubscribe to pound@apsis.ch.<br>
Please contact roseg@apsis.ch for questions.<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Read my blog @ <a href="http://www.raven.nu/blog">http://www.raven.nu/blog</a><br>