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

option #1 would be nginx do the mysql connection itself. option #2 would be nginx just connects to the tracker (this is probably best) since it's a simple socket connection

location /media/ { mogilefs on; mogilefs_domain images;

option #1 mogilefs_tracker_username mogilefs; mogilefs_tracker_password foo; mogilefs_tracker_host 192.168.1.203; mogilefs_tracker_database mogilefs;

option #2 mogilefs_tracker_host 192.168.1.202:7001;

and perhaps something like mogilefs_key_style hash; ? or something... (used to determine how the keys are actually setup) }

I think the biggest missing piece of the puzzle is how to determine the key structure. Otherwise I am sure it's quite simple, and it uses dav/HTTP to retrieve the files anyway, so the C code needed would be:

option #1: 1) mysql client 2) something which can do efficient HTTP GETs with offset support (probably already in nginx)

option #2: 1) something that can do a simple socket connect, ask the tracker for info, and then pass it on to step 2 (probably already in nginx) 2) something which can do efficient HTTP GETs with offset support (probably already in nginx)

If I knew anything worthwhile in C I would try it myself. I am sure someone even with basic C skills could hack it up really quick. It just needs one socket to talk to the tracker, then depending on the reply, open a second connection to grab the file...

On 4/28/08, kingler <king...@public.gmane.org> wrote: