SCGI is so simple that its pretty much impossible to implement wrongly. The only brokenness that I've seen is that nginx' SCGI handler (Which is a somewhat unmaintained 3rd party module) doesn't accept status: lines like its supposed to. The work around took one line, however. If I ever get around to overhauling said module, then I'll fix it.
On 31 May 2010 17:27, Paul Ruizendaal <p...@planet.nl> wrote: > > > The biggest issue with HTTP 1.1 for backend communication is long > > running connections since HTTP doesn't support interleaving. > > Now that I find a convincing argument! > > Can you confirm from your experience that SCGI is not broken in this > respect in the same way as FastCGI (i.e. the protocol spec defines it, but > most code doesn't implement it or is broken)? > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
