Hi,
I'm trying to work on this problem. I have an npm that extends
node-http-proxy to provide round-robin and sticky-sessions support, I built
an option to use Redis as the persistent memory store so that you could use
cluster, but there's a bug somewhere so I might need help fixing that. The
There are a couple ways to do this.
1. Use a session store that is transactional and shared (redis etc.) and
store where a session should be forwarded to.
2. Use a hashing method that will consistently point to the same
location/worker for the same session (session could be ip/user/etc.), if
th
Does the node clustering module provide hooks to achieve this (sticky
sessions) or will I have to re-implement a bunch of things from scratch or
copy-paste code?
On Friday, June 22, 2012 8:08:30 AM UTC-7, Bradley Meck wrote:
>
> There are a couple ways to do this.
>
> 1. Use a session store that
Just saw the blog post introducing 0.8 and it seems that it's a conscious
decision to leave sticky sessions out.
On Sunday, June 24, 2012 10:28:17 PM UTC-7, dhruvbird wrote:
>
> Does the node clustering module provide hooks to achieve this (sticky
> sessions) or will I have to re-implement a bun
I read in the docs some place. I cant seems to find it again. Can anyone say
anything about where information might be on this?
On Tuesday, June 26, 2012 10:54:04 PM UTC-4, Dominic wrote:
> I understand that the cluster api works by passing a file descriptor
>
> to the worker process.
>
>
>
>
On Tue, Jun 26, 2012 at 6:02 AM, dhruvbird wrote:
> Just saw the blog post introducing 0.8 and it seems that it's a conscious
> decision to leave sticky sessions out.
That's correct.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Post
+1 for not including this, sticky sessions are painful when they become the
least common denominator.
On Tuesday, June 26, 2012 8:48:00 AM UTC-5, Ben Noordhuis wrote:
>
> On Tue, Jun 26, 2012 at 6:02 AM, dhruvbird wrote:
> > Just saw the blog post introducing 0.8 and it seems that it's a
> con
For sessions, I recommend using redis with redsess:
https://github.com/isaacs/redsess
On Tue, Jun 26, 2012 at 7:58 AM, Bradley Meck wrote:
> +1 for not including this, sticky sessions are painful when they become the
> least common denominator.
>
>
> On Tuesday, June 26, 2012 8:48:00 AM UTC-5, Be
I understand that the cluster api works by passing a file descriptor
to the worker process.
is it possible pass a file descriptor after you have started reading from it?
On Wed, Jun 27, 2012 at 9:30 AM, Isaac Schlueter wrote:
> For sessions, I recommend using redis with redsess:
> https://github