atom feed25 messages in ru.sysoev.nginxRe: A hardware question
FromSent OnAttachments
mikeApr 27, 2008 12:36 am 
Dave CheneyApr 27, 2008 1:21 am 
mikeApr 27, 2008 1:58 am 
Dave CheneyApr 27, 2008 2:11 am 
mikeApr 27, 2008 1:34 pm 
Janko HauserApr 27, 2008 1:44 pm 
Igor SysoevApr 27, 2008 9:34 pm 
mikeApr 27, 2008 10:52 pm 
Igor SysoevApr 27, 2008 11:05 pm 
Chavelle VincentApr 28, 2008 3:16 am 
Igor SysoevApr 28, 2008 7:10 am 
mikeApr 28, 2008 11:45 am 
kinglerApr 28, 2008 12:03 pm 
mikeApr 28, 2008 12:26 pm 
Ezra ZygmuntowiczApr 29, 2008 3:11 pm 
mikeApr 29, 2008 4:55 pm 
mikeApr 29, 2008 7:25 pm 
mikeApr 29, 2008 9:11 pm 
Manlio PerilloApr 30, 2008 1:11 am 
mikeApr 30, 2008 2:09 am 
Manlio PerilloMay 1, 2008 2:47 am 
mikeMay 1, 2008 8:17 am 
mikeMay 1, 2008 3:11 pm 
Eden LiMay 1, 2008 6:31 pm 
mikeMay 1, 2008 7:03 pm 
Subject:Re: A hardware question
From:Manlio Perillo (manl@public.gmane.org)
Date:Apr 30, 2008 1:11:44 am
List:ru.sysoev.nginx

mike ha scritto:

[talking about a MogileFS module for Nginx]

I think it would be something worthwhile myself.

Just needs parameters - the tracker database info, and the domain right? Then you just use the domain + key to get the file. Maybe domain isn't even required.

However, wouldn't you need some sort of logic to determine how to create the key?

Some people use an md5 of the URI I guess, so it would be something like

foo.com/media/abc72849482bc8398af98effd9g843

/media/ would be mapped to something like

I think that the better solution is to extend the nginx upstream module so that the list of backend servers (address, port and weight) can be obtained at request runtime, and not only at configuration time.

This means that a module should only implement the logic to obtain the backends list, and all the work can be done by Nginx.

However this assumes that on every backend, the URI to the file is the same (but this should not be a problem, if Nginx is on each node).