3 ms·
On a related note, I have created the SPike daemon: git://devel2.cuci.nl/spike . It's written in Pike, is being actively maintained, with roughly the following
by BuGlessRB 4y ago
On a related note, I have created the SPike daemon: git://devel2.cuci.nl/spike .
It's written in Pike, is being actively maintained, with roughly the following featureset:
- Meaningful error messages on compiled modules.
- Smart auto-recompilation of modules (mtime based).
- Auto-fallback to last-known-good modules on compilation failure.
- Two classes for module development: Spike.Base and Spike.Site
+ Spike.Base implements a log() and listenport() primitive.
+ Spike.Site adds filesystems, databasepools and a configuration system
per site.
- Live configuration reload through SIGHUP (no downtime).
- Integrated HTTP and WebSocket dispatch engine.
- Transparent proxy support.
- Auto-gzip compression on both static and dynamic content.
- Integrated and configurable logging mechanism to syslog.
- Completely Shuffler-ised (maximal offloading of communication overhead to
pure C and the kernel).
- Less filling: 29KB of source code (single file).
- em-bee 4y agointeresting, is there more documentation, examples? are there similar systems in other languages so people can get an idea what to compare it to? btw, welcome to hackernews. everyone, if you didn't already recognize the nickname, BuGlessRB is famous for being the creator of procmail :-)
- BuGlessRB 4y agoI have several active implementations now (in active use for the past 2 years), I guess I could easily water some of those down into a few examples. With regard to similar systems... Good question. Comparable solutions: - Ruby Passenger daemon. Almost feature parity with the Enterprise version, except for the "cool robot logo". - Python Flask framework. - Apache with mod_php or php-fpm. - Roxen. With respect to procmail, yes, indeed, and I picked up its maintenance again, and released a new version recently.