Re: Directors user sessions

2008-05-29 Thread Cherife Li
Sorry for this *late* response. Noticed this mail while searching the ML archive just now. I missed it. :-( On Mon, Apr 7, 2008 at 4:55 AM, Erik Torlen [EMAIL PROTECTED] wrote: But the loadbalancing is already implenteed. I dont see why it shouldn't be used as loadbalancer if the functionality

Re: Directors user sessions

2008-04-06 Thread Erik Torlen
But the loadbalancing is already implenteed. I dont see why it shouldn't be used as loadbalancer if the functionality exists? I don't want to use one place for all sessions, like a file share or something in that direction. Im thinking about creating a Header that is called X-Backend: (a|b|c|d).

Directors user sessions

2008-03-28 Thread duja
Hi, I got a question regarding the Directors in varnish vcl. If user A is logging in to http://mywebsite.com and the website is using varnish (with directors) in front of 4 backend servers. The 4 backend servers is identical. User A is logging in and hits server 1. He then goes to his profile

Re: Directors user sessions

2008-03-28 Thread Cherife Li
On 2008-3-28 19:05, [EMAIL PROTECTED] wrote: Hi, I got a question regarding the Directors in varnish vcl. If user A is logging in to http://mywebsite.com and the website is using varnish (with directors) in front of 4 backend servers. The 4 backend servers is identical. User A is

Re: Directors user sessions

2008-03-28 Thread Florian Engelhardt
On Fri, 28 Mar 2008 12:05:23 +0100 [EMAIL PROTECTED] wrote: Hi, I got a question regarding the Directors in varnish vcl. If user A is logging in to http://mywebsite.com and the website is using varnish (with directors) in front of 4 backend servers. The 4 backend servers is identical.

Re: Directors user sessions

2008-03-28 Thread Michael S. Fischer
On Fri, Mar 28, 2008 at 4:58 AM, Florian Engelhardt [EMAIL PROTECTED] wrote: You could store the sessions on a separate server, for instance on a memcache or in a database Good idea. (Though if you use memcached, you'd probably want to periodically copy the backing store to a file to survive