[pLog-svn] resserver usage

Oscar Renalias oscar at renalias.net
Wed Oct 4 06:41:05 GMT 2006


> I think maybe x-sendfile is an alternative way. Take a look at the following
> links:
>
> http://blog.thinkphp.de/plugin/tag/lighttpd
>http://wiki.rubyonrails.org/rails/pages/HowtoSendFilesFast
> http://celebnamer.celebworld.ws/stuff/mod_xsendfile/
>
> 1. Maybe we can add this as an alternative option. So, if user install mod_x_sendfile,
> we can send the file through x_sendfile header instead of
> php put.

This could be used as an alternative and it doesn't look too difficult
to implement.

I understand you've already used this for one of your projects, right?

> 2. Maybe we can simplify our resserver.php. Change it to a single exist
> script instead of depends on those DAOs, Actions, Views, ..... But it might
> be break some principle of lifetype framework ... :(

I don't think that's the problem, although it can be easily verified.
I thing the problem lies in sending the file, as PHP's fread() will
never probably as fast as Apache's native system calls.

If I have some time I will create a script that behaves as
resserver.php but without the action/view part, let's see if it works
faster.

> I personally like to keep the script there. Not for compatability, it is for
> access permission. Without wraping with php script, it is not easy to do the
> access control.
>
> And, I only has one concern about plugin/mod_rewrite method.
>
> If I have 10000 blogs, will the rules grows to 10000 rules? Will this casue
> the apache performance down?

I was going to ask the same thing. How well does this scale? How fast
can Apache handle a 3-4mb .htaccess file with tens of thousands of
rules? How fast could the plugin add the 12332nd rule to a big
.htaccess file?

Oscar


More information about the pLog-svn mailing list