On Sun, Aug 11, 2013 at 03:20:14PM +0200, Stephan Beal wrote: > On Sun, Aug 11, 2013 at 3:18 PM, Stephan Beal <[email protected]> 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.
Well . . . that'd definitely change how I would want to do things, then. Now that I think about it, though, I'm not sure I'd want to go the CGI route if I needed a whole separate webserver, anyway. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
