Correction: After closer examination of CGI
directory in mod_haskell I found that the
library is strictly bound to a single concept
of using it as Apache loadable module.
Another words, one cannot use it as is in
other modes of operations, for example in fastCGI
mode. Or did I miss something here?
By fastCGI I understand either official one,
or home grown solution which I can easily provide
via pipes to runhugs or hugs. I can obviously modify
your library it to suit my needs, but wouldn't
it be better to provide a support for either
approach and let us made our minds how we want
to use it? I am sure everyone would benefit
from such a clear separation of functionalities.
Jan
