On Wed, Mar 12, 2014 at 06:31:29PM +0100, Ramon Ribó wrote: > > > The current Fossil implementation runs a separate process for each HTTP > > request. So an in-memory cache wouldn't be helpful. It has to be disk- > > based. > > Does not FastCGI do exactly the opposite?
The current implementation simply uses a fork() per request. Not fork+exec, which is the common case (CGI) FastCGI is meant to improve. AFAIU, using a separate process eases the heap memory handling. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
