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
Jim,
I'd be happy to merge in my write-up about the TH1 script language.
Howver, that is not "quick start guide" material, and perhaps is outside
the focus of the document.
Paul
On Sat, 29 May 2010 06:20:01 -0400, Jim Schimpf
wrote:
> Hi,
>
> I've been working on this for a while and thou
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
main
On May 29, 2010 18:59:30 PDT, Richard Hipp wrote:
> If I had a web server at hand that would do SCGI, I might consider
> adding the "fossil scgi" command for you. But as I don't; I have no
> way to test the "fossil scgi" command.
FYI, mod_scgi provides SCGI support in Apache. The sources ar
On 30 May 2010 02:59, Richard Hipp wrote:
>
> "CGI ... is highly inefficient". The http://www.sqlite.org/ and
> http://www.fossil-scm.org/ websites are both run off of the same server
> (check the IP addresses on the domains). The HTTP server there is a simple
> home-brew job implemented as a si
On Sat, 2010-05-29 at 21:59 -0400, Richard Hipp wrote:
> The http://www.sqlite.org/ and http://www.fossil-scm.org/ websites
> are both run off of the same server ... This server takes over a
> quarter million requests per day, 10GB of traffic/day, and it does
> so using less than 3% of of the CPU o
6 matches
Mail list logo
