On Wed, Mar 12, 2014 at 6:31 PM, Ramon Ribó <ram...@compassis.com> 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? > FastCGI requires that there be some sort of state object which is can re-set between calls, and feed that state into each child. Fossil doesn't have such a state object (it has one, but not one which can simply be re-set/re-used), so FastCGI can't really do its magic with fossil. libfossil (currently under construction and moving along nicely) provides such a construct. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
