Handle perlbal requests with a perl subroutine
This module allows responses to be handled with a simple \s-1API\s0 that's similar in principle to \s-1CGI\s0, mod_perl response handlers, etc.
It does not, however, come anywhere close to conforming to the \s-1CGI\s0 \*(L"standard\*(R". It's actually more like mod_perl in usage, though there are several differences. Most notably, Perlbal is single-process and single-threaded, and handlers run inside the Perlbal process and must therefore return quickly and not do any blocking operations.
As it currently stands, this is very bare-bones and has only really been used with basic \s-1GET\s0 requests. It lacks a nice \s-1API\s0 for handling the body of a \s-1POST\s0 or \s-1PUT\s0 request.
It is not recommended to use this for extensive applications. Perlbal is first and foremost a load balancer, so if you're doing something at all complicated you're probably better off using something like Apache mod_perl and then putting Perlbal in front if it if necessary. However, this plugin may prove useful for simple handlers or perhaps embedding a simple \s-1HTTP\s0 service into another application that uses \*(C`Danga::Socket\*(C'.
This module provides a Perlbal plugin which can be loaded and used as follows.
LOAD cgilike PERLREQUIRE = MyPackage CREATE SERVICE cgilike SET role = web_server SET listen = 127.0.0.1:80 SET plugins = cgilike PERLHANDLER = MyPackage::handler ENABLE cgilike
With this plugin loaded into a particular service, the plugin will then be called for all requests for that service.
Set cgilike.handler to the name of a subroutine that will handle requests. This subroutine will receive an object which allows interaction with the Perlbal service.
package MyPackage sub handler { my ($r) = @_; if ($r->uri eq '/') { print "<p>Hello, world</p>"; return Perlbal::Plugin::Cgilike::HANDLED; } else { return 404; } }
Return \*(C`Perlbal::Plugin::Cgilike::HANDLED\*(C' to indicate that the request has been handled, or return some \s-1HTTP\s0 error code to produce a predefined error message. You may also return \*(C`Perlbal::Plugin::Cgilike::DECLINED\*(C' if you do not wish to handle the request, in which case Perlbal will be allowed to handle the request in whatever way it would have done without Cgilike loaded.
If your handler returns any non-success value, it \s-1MUST\s0 \s-1NOT\s0 produce any output. If you produce output before returning such a value, the response to the client is likely to be utter nonsense.
You may also return \*(C`Perlbal::Plugin::Cgilike::POSTPONE_RESPONSE\*(C', which is equivalent to returning zero except that the \s-1HTTP\s0 connection will be left open once you return. It is your responsibility to later call \*(C`$r->end_response()\*(C' when you have completed the response. This style is necessary when you need to perform some long operation before you can return a response; you'll need to use some appropriate method to set a callback to run when the operation completes and then do your response in the callback. Once you've called \*(C`end_response\*(C', you must not call any further methods on $r; it's probably safest to just return immediately afterwards to avoid any mishaps.
\s-1TODO:\s0 Write this
Currently there is no \s-1API\s0 for dealing with the body of a \s-1POST\s0 or \s-1PUT\s0 request. Ideally it'd be able to do automatic decoding of application/x-www-form-urlencoded data, too.
The \s-1POSTPONE_RESPONSE\s0 functionality has not been tested extensively and is probably buggy.
Copyright 2007 Martin Atkins <[email protected]> and Six Apart Ltd.
This module is part of the Perlbal distribution, and as such can be distributed under the same licence terms as the rest of Perlbal.