G-WAN is a web server, with a small-footprint (50 KB). It supports GET, HEAD, POST, PUT, DELETE and OPTIONS, conditional requests and directory listings. G-WAN is also provably safer (speed is a side-effect of good designs).
G-WAN's C servlets (that you just 'edit & play') are as fast as static content (you can benchmark the 'hello.c' servlet against a PHP, Perl, Java or ASP.Net equivalent).
Why use C rather than a 'safer' language for G-WAN servlets:
Perl, PHP, Java, ASP.Net and G-WAN are written in C, for a reason.
If you already know C, how many languages do you need to learn?
C can be as safe as any other language (see the 'crash.c' servlet). The best way to understand G-WAN's capabilities is to play with it!
What's New in This Release: [ read full changelog ]
· implemented a 'Lorenz waterwheel'-inspired logic for scalability & speed
· added support for real-time cache updates -without speed penalty (no more G-WAN stop/restart to reload updated docs/servlets)
· added support for the If-Not-Match header field (ETag's companion)
· different log files are created for each new day, keeping files smaller
· local time offsets in the access.log file time-stamps use daylight savings
· too short requests receive '400:Bad Request' rather than '404:Not Found'
· restored support for absolute URIs (disabled by too stringent checks).
Find us on Google+
