Hello Justin,
Pound already does this. Once a connection is established, that connection
can be bound using the session configuration:
Session
Type IP
TTL xxx
End
That will keep the IP address of the client bound to the same BE. I know
this works because I use it and would not be able to have my applications
work if it didn't work.
-- jake
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Tuesday, January 27, 2009 9:15 AM
> To: [email protected]
> Subject: Re: [Pound Mailing List] Session Affinity and Backend
> Determination
>
> > 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.
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
