in reply to setting lighttpd/fcgi/perl ?

I recently released FCGI::Engine, which is meant to fill in what I see as the missing tools for Perl based Fast CGI development. It is modeled very heavily on Catalyst::Engine::FastCGI, but also includes a refactored FCGI::ProcManager as well. The SYNOPSIS section of FCGI::Engine pretty much says it all, although if you have any questions feel free to email me.

I use Lighttpd as well, so it also includes some Lighttpd conf files that are used in the tests.

While this module is only 0.02, I consider it pretty stable. For one thing, I "appropriated" all the really smart/hard bits from other more established modules (Catalyst::Engine::FCGI and FCGI::ProcManager) and just made them more generic (i.e. not tied to Catalyst). Also, this is currently being used to manage 6 different FCGI backends for a large $work project and has been running without issue for almost 4 months now.

-stvn

Replies are listed 'Best First'.
Re^2: setting lighttpd/fcgi/perl ?
by rootcho (Pilgrim) on Feb 03, 2008 at 06:22 UTC
    thanx , going to check it... and test.. definetly will ask more ;)
Re^2: setting lighttpd/fcgi/perl ?
by rootcho (Pilgrim) on Feb 04, 2008 at 01:51 UTC
    from what I understand you set handler() function in a module to do the job.
    How do you normally do url-2->method dispatching ?

    and one more thing if I don't specify bin-path config option in lighttpd config then I have to start this handler-script separately with some options (and this is what they call in lighty docs runnging fcgi as external-fcgi-server), right ?
      from what I understand you set handler() function in a module to do the job.

      That is the default, you can change it with the handler_method constructor option. (NOTE: this was broke in any pre-0.03 release)

      How do you normally do url-2->method dispatching ?

      Usually the web framework I am using will take care of this (Catalyst, CGI::Application, etc). FCGI::Engine is simply about managing FCGI details for you, this kind of stuff is outside of the scope of this module.

      and one more thing if I don't specify bin-path config option in lighttpd config then I have to start this handler-script separately with some options (and this is what they call in lighty docs runnging fcgi as external-fcgi-server), right ?

      Yes, take a look at FCGI::Engine::Manager for a simple way to do this, the docs are still a little slim but if you look at the "020_basic_manager.t" test file and the contents of t/conf/ and t/scripts/ you will see how it is configured.

      -stvn
        How do you normally do url-2->method dispatching ?

        Usually the web framework I am using will take care of this (Catalyst, CGI::Application, etc). FCGI::Engine is simply about managing FCGI details for you, this kind of stuff is outside of the scope of this module.

        I meant if I want to do it ;) ? I'll take a look at the frameworks, but !
        I would be using it to flush JSON structures and from time to time some html page and rather do it manually than using framework.