…fore sending the data to the HTTP client. This allows backend processes to stream data.
…he spawn manager.
…which it is not necessary." This reverts commit fa8f9eb.
…f wrongly reporting that they're found. Fix typo.
This bug seems to be what causes more backend processes to be spawned than is allowed by the 'max' setting.
…t raise an exception if said library is not available.
…for better portability.
Some people reported that 'count' can go over 'max'. This is the cause, I suspect.
…t was used to run the installer, instead of the Rake that's in PATH. Update the gem installation instructions so that the RubyGems command that belongs to the Ruby interpreter that was used to run the installer is preferred.
… that was used to run the installer. It makes installation on Ruby Enterprise Edition less error-prone.
…d to application_controller.rb.
(See full trace by running task with --trace) We could do this by inspecting ARGV, or the ENV. I chose the latter. Setting ENV['TRACE'] will now pass --trace to rake. Should probably document that somewhere.
The are not neccessarily installed in the same --prefix (see ./configure) (note, the apu-1-config does not accept the --cppflags option With my email@example.com HTTPD PMC hat on: Technicallly, this is still wrong, this should be using apxs alone, but that would have required me to refactor this and I did not have time at the moment. For an example of the correct way to do this, see the apreq (libapreq2) httpd module (c-binding portion). [firstname.lastname@example.org] Note, Eventually, httpd will have an httpd-config similiar to gnome-config, neon-config, serf-config, etc.... at which point it should switch to that.
… fork()+exec() or a system() inside the application properly closes the connection to the web server.
cache_template_loading is removed from Rails 2.2.