Commits on Oct 12, 2008
  1. Working out failure behavior.

    The process that call ifastcgi:add_server/4 will be linked to by
    the started server. This makes sure resources are freed.
    The started server is also added as a temporary worker in the
    supervisor which means it will not be restarted by the supervisor
    on failure.
    The idea is that we bring down the application that started the
    server instead.
    committed Oct 12, 2008
Commits on Oct 11, 2008
  1. Work

    committed Oct 11, 2008
  2. Supress dialyzer complaints

    committed Oct 11, 2008
  3. Warn about missing type specs

    committed Oct 11, 2008
Commits on Sep 21, 2008
  1. Fixing the application-ness, removing some debug output

    It all still feels pretty fragile, but it works when i test it with
    nginx. This is what I do:
    cd src
    erl -make
    erl -pa ../ebin/
    1> application:start(sasl). %% Because it is noisy a nice.
    2> application:start(ifastcgi). %% Because it is needed
    3> ifastcgi:add_server(6464, ifastcgi_test, args).
    And a server listening on localhost in ngnix has the following:
    	location /fcgi {
    		fastcgi_pass	localhost:6464;
    Pointing my browser at the server I set up in my ngnix for the path
    /fcgi/fooobazy gives me this page:
    Hello world!
    HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:
    Gecko/2008072820 Firefox/3.0.1
    HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5
    HTTP_ACCEPT_ENCODING: gzip,deflate
    HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    HTTP_CONNECTION: keep-alive
    HTTP_CACHE_CONTROL: max-age=0
    That's it. Pretty cool for 8 work hours worth of weekend hack.
    committed Sep 21, 2008
  2. Emakefile that compile into ../ebin

    committed Sep 21, 2008
  3. A single-ported fastcgi server.

    committed Sep 21, 2008
Commits on Sep 20, 2008
  1. A FastCGI server in Erlang.

    committed Sep 20, 2008