Description:

*WARNING:* This module's API may change without warning. Also, the docs are
somewhat incomplete and out of date. I will be fixing this soonish.

The synopsis makes this module sounds much more complicated than it
actually is. the AnyEvent::Task manpage is a fork-on-demand but
persistent-worker server (the AnyEvent::Task::Server manpage) combined with
an asynchronous interface to a request queue and pooled-worker client (the
AnyEvent::Task::Client manpage). Both client and server are of course built
with the AnyEvent manpage because it's awesome. However, workers can't use
AnyEvent (yet).

A server is started with 'AnyEvent::Task::Server->new'. This should at
least be passed the 'listen' and 'interface' arguments. Keep the returned
server object around for as long as you want the server to be running.
'interface' is the code that should handle each request. See the interface
section below for its specification. A 'setup' coderef can be passed in to
run some code when a new worker is forked. A 'checkout_done' coderef can be
passed in to run some code whenever a checkout is released (see below).