----- Original Message -----
> Hi nginx-devel,
>
>
> I'm new to the world of nginx development. I'm looking at patching
> nginx to allow for configurable session caching via memcached. Goal is
> to be able to session cache across boxes within a cluster when there's
> no guarantee that a client will connect to the same box each time.
>
>
> I've seen this previous work from mpalmer:
> https://github.com/mpalmer/nginx/compare/0.8.x...memcache-ssl-0.8
>
>
>
> However it is 3 years old. I'm going to look at patching it onto the
> mainline and auditing the code to see if it still makes sense.
>
>
> A few questions.
> 1) Is there anything I should look out for / be careful of?
> 2) Is there any desire for this feature on mainline? If so, any
> suggestions on how to request feedback. Via patches to the mailing
> list?


http://trac.nginx.org/nginx/ticket/120#comment:8

(Just a side note: Matt Palmer's patches are classic example of what shouldn't be done in nginx. He uses blocking remote memcached calls, and this is something one shouldn't even think about as this will block the whole nginx worker and all clients.)


On another note, there is session tickets in files now implemented that can be distributed. Sessions however are different.


--
Daniel Black, Engineer @ Open Query (http://openquery.com.au)
Remote expertise & maintenance for MySQL/MariaDB server environments.

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel