Nginx feature request

Hendrik Hardeman hendrik.hardeman at hotmail.com
Mon Feb 11 01:21:40 MSK 2008


eliott,

Thanks for the suggestion.

The solution you offer seems workable for a smaller number of files, but I'm not sure how such a cron job would scale with lots of files (potentially thousands) added and deleted on a regular basis. Cron jobs also require cpu time and harddisk access - even more so if I'd want a finer resolution than 5 minutes.

I'd rather rely entirely on the filesystem itself. Just create a file with the appropriate mtime (with a resolution of seconds rather than minutes) and then forget about it - as nginx could take care of the rest. Replicating / scaling would also be very straightforward.

Well, just an idea. Is probably not very useful for anyone else, so I don't expect much support for my feature request :) Will probably end up implementing it myself.

Hendrik

 

> Date: Sun, 10 Feb 2008 13:13:51 -0800
> From: eliott at cactuswax.net
> To: nginx at sysoev.ru
> Subject: Re: Nginx feature request
> 
> How about a cron job that runs every 5 minutes, and sets a file with a
> future mtime as non readable, and a past mtime as readable?
> 

_________________________________________________________________
Post free property ads on Yello Classifieds now! www.yello.in
http://ss1.richmedia.in/recurl.asp?pid=219
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080211/302df6cd/attachment.html>


More information about the nginx mailing list