Tree
- Tree:
039725d48dacf6ac3d5d0115f30da1c63ad1f732
- Date:
- Message:
- one FastCGI connection per client FastCGI is designed to multiplex requests over a single connection, so ideally the server can open only one connection per worker to the FastCGI application and that's that. Doing this kind of multiplexing makes the code harder to follow and easier to break/leak etc on the gmid side however. OpenBSD' httpd seems to open one connection per client, so why can't we too? One connection per request is still way better (lighter) than using CGI, and we can avoid all the pitfalls of the multiplexing (keeping track of "live ids", properly shut down etc...)
Dockerfile | commits | blame |
README | commits | blame |
gmid | commits | blame |
gmid.service | commits | blame |
vim/ |
README
This directory is for additional contributed files which may be useful. Dockerfile Sample Dockerfile to build alpine-based gmid images. gmid Sample rc(8) script for OpenBSD, to be placed in /etc/rc.d. gmid.service Simple systemd service file. vim Syntax highlighting of gmid configuration for vim, to be placed into ~/.vim/ or /usr/share/vim/vimfiles/. To enable Syntastic checker, put this line in your vimrc: let g:syntastic_gmid_checkers = ['gmid']