AnyEvent::MessagePack is MessagePack stream serializer/deserializer
for AnyEvent.
Abstract framework for RPC clients.
Run a process or coderef asynchronously
Flexible, OO, asynchronous process spawning and management.
Manage blocking task in external process.
AnyEvent provides an identical interface to multiple event loops.
This allows module authors to utilise an event loop without forcing
module users to use the same event loop (as only a single event loop
can coexist peacefully at any one time).
The interface itself is vaguely similar but not identical to the Event
module.
On the first call of any method, the module tries to detect the
currently loaded event loop by probing wether any of the following
modules is loaded: Coro::Event, Event, Glib, Tk. The first one found
is used. If none is found, the module tries to load these modules in
the order given. The first one that could be successfully loaded will
be used. If still none could be found, AnyEvent will fall back to a
pure-perl event loop, which is also not very efficient.
AnyMQ is message queue system based on AnyEvent. It can store all messages in
memory or use external message queue servers.
App::Build is a module which extends Module::Build.
It is used to install whole applications rather than
merely perl modules.
The App::Cache module lets an application cache data locally. There are a
few times an application would need to cache data: when it is retrieving
information from the network or when it has to complete a large
calculation.
For example, the Parse::BACKPAN::Packages module downloads a file off the
net and parses it, creating a data structure. Only then can it actually
provide any useful information for the programmer.
Parse::BACKPAN::Packages uses App::Cache to cache both the file download
and data structures, providing much faster use when the data is cached.
This module stores data in the home directory of the user, in a dot
directory. For example, the Parse::BACKPAN::Packages cache is actually
stored underneath "~/.parse_backpan_packages/cache/". This is so that
permissions are not a problem - it is a per-user, per-application cache.
Pack your dependencies onto your script file.