Can't you solve that client-side? Some scripts don't send a body either.by Olaf van der Spek - Ideas and Feature Requests
The refresh should be non-blocking, so there won't be any waiting. Millions is quite a large number. :p If you do have a very large number of infrequently used vhosts then a more complex design *might* be better. But I'd start with the simple design.by Olaf van der Spek - Ideas and Feature Requests
Yesby Olaf van der Spek - Ideas and Feature Requests
About 1 per minuteby Olaf van der Spek - Ideas and Feature Requests
That's not a large number. :p You're joking when you say 1 database request per HTTP request, right?by Olaf van der Spek - Ideas and Feature Requests
> That's quite interesting having it refresh. Would > that put much of a strain on the running of > things? Particular for ISPs like the one Neil is > representing with large numbers of vhosts? Or What's a large number?by Olaf van der Spek - Ideas and Feature Requests
A simple way to configure vhosts would be to use the host name as part of the doc root. Like root = /srv/<host>/htdocs Could you support this? http://redmine.lighttpd.net/wiki/1/Docs:ModSimpleVhostby Olaf van der Spek - Ideas and Feature Requests
Reading the data (from the DB) on startup is easy, refreshing it every X minutes is a bit harder but quite doable.by Olaf van der Spek - Ideas and Feature Requests
Somebody?by Olaf van der Spek - Nginx Mailing List - English
> I've posted some patches which change things as > part of keepalive > with backends work, but most likely you don't want > to rely on > them. You may want to make your app actually Is there an bug/issue tracker that tracks this?by Olaf van der Spek - Nginx Mailing List - English
> nginx doesn't process data from fastcgi app untill > buffer filled or > connection closed by app (as required per spec > without > FCGI_KEEP_CONN flag set). What part of the spec requires the webserver to wait until the connection is closed by the backend? Doesn't Nginx support (and use) persistent connections?by Olaf van der Spek - Nginx Mailing List - English
Maxim Dounin Wrote: > Most likely your backend doesn't honor > FCGI_KEEP_CONN flag. It doesn't. Why does Nginx wait after FCGI_END_REQUEST though?by Olaf van der Spek - Nginx Mailing List - English
I've got a self-written FastCGI backend. It works with Lighttpd, but not with Nginx. Nginx connects to the backend, sends the request, receives the response, but then appears to wait on something else. The backend writes one or more FCGI_STDOUT packets and a FCGI_END_REQUEST packet. Any hints on what's wrong? writev(10, [{"\1\1\0\1\0\10\0\0\0\1\0\0\0\0\0\0\1\4\0\1\3\212\6\0\f\0QUERY_&quby Olaf van der Spek - Nginx Mailing List - English
Oops, wrong forum, could a mod move it please?by Olaf van der Spek - Ideas and Feature Requests
I've got a self-written FastCGI backend. It works with Lighttpd, but not with Nginx. Nginx connects to the backend, sends the request, receives the response, but then appears to wait on something else. The backend writes one or more FCGI_STDOUT packets and a FCGI_END_REQUEST packet. Any hints on what's wrong? writev(10, [{"\1\1\0\1\0\10\0\0\0\1\0\0\0\0\0\0\1\4\0\1\3\212\6\0\f\0QUERY_&quby Olaf van der Spek - Ideas and Feature Requests