On Sun, Aug 11, 2013 at 9:20 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> > On Sun, Aug 11, 2013 at 3:18 PM, Stephan Beal <sgb...@googlemail.com>wrote: > >> Fossil is not fastcgi-compatible. i tried to get it working a few years >> ago but fastcgi requires that each execution of the app has a clean >> starting state, and fossil's app is built to work only for a single >> execution. >> > > That wasn't terribly clear. FastCGI basically starts 1 instance of the app > and keeps feeding it new data for each request. Fossil's structure does not > allow it to do that. > > Does too. For Fossil to run FastCGI/SCGI, all that is needed is another command similar to "fossil server" or "fossil ui". The "fossil server" listens for incoming HTTP requests and responds separately to each request. A "fossil fastcgi" or "fossil scgi" command would do basically the same thing, except that it would interpret the FastCGI or SCGI wire protocol rather than HTTP. Fossil does not support FastCGI or SCGI simply because I do not have ready access to a webserver that supports those things and hence no way to test any proposed implementation. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
