Hi folks,

Two remarks:

1. I'm happy that more and more people are contributing to Fossil, but I'm
also a bit concerned about the increasing Posix dependence. The https code
builds in a dependence on libssl, and now the below patch is Posix only.
The cross-platform nature of Fossil is important to me, as is the small
binary (i.e. no dependence on cygwin, wine, jre, ...)

2. What is the added value of scgi? What can scgi do that http can't? What
I mean is, running Fossil as http server and configuring the front server
(ngix in the original post) as a reverse proxy solves the exact same
problem without any need for additional code. Perhaps I'm missing the
point, but to me adding scgi is bloat.

Paul


On Sun, 30 May 2010 21:23:59 +0100, Owen Shepherd <owen.sheph...@e43.eu>
wrote:
> I've finished modifying Fossil to support SCGI. Some notes:
> 
>    - I rewrote the accept loop of the server/ui command at the same
time.
>    It
>    no longer uses select with a timeout in order to reap child
processes;
>    instead, a signal handler is installed for SIGCHLD in order to reap
>    them and
>    maintain the child process count. This both means Fossil doesn't wake
up
>    pointlessly every 60 seconds, and that the code is much simpler.
>    - Instead of calling sleep when too many connections have been
>    established for an arbritary time period with a minimum length of 2
>    seconds,
>    we call pause() until the number of connections drops to a
satisfactory
>    level.
> 
> (In fact, both SCGI and HTTP modes share an accept loop).
> 
> fossil scgi performs admirably behind Apache with mod_scgi. It works
fine
> for GET requests behind nginx' mod_scgi; but POST requests cause it to
lose
> its marbles. This is an issue on nginx' end; I'll have to look into
that.
> 
> scgi is currently only supported on !win32 because I don't have any
> experience with winsock. Additionally, as with Fossil's standard server
> handler, it depends upon fork.
> 
> Support is provided for both TCP and Unix domain sockets. Which to use
is
> determined by whether the port parameter is an integer or not.

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to