Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
Sympa::Spindle::DispatchRequest(3Sympa)
Workflow to dispatch requests
XtAppNextEvent(3), XtAppPending(3), XtAppPeekEvent(3), XtAppProcessEvent(3), XtDispatchEvent(3), XtAppMainLoop(3)
query and process events and input
XtInsertEventTypeHandler(3), XtRemoveEventTypeHandler(3), XtRegisterExtensionSelector(3), XtSetEventDispatcher(3), XtDispatchEventToWidget(3)
extension event handling
XtRegisterDrawable(3)
register a drawable with the Intrinsics event dispatcher
ck_epoch_barrier(3)
block until a grace period and all callbacks have been dispatched
ck_epoch_poll(3)
non-blocking poll of epoch object for dispatch cycles
cmap_dispatch(3)
Dispatches callbacks from the CMAP service
cmap_fd_get(3)
Dispatches callbacks from the CMAP service
cpg_dispatch(3)
Dispatches callbacks from the CPG service
cpg_fd_get(3)
Dispatches callbacks from the CPG service
ezmlm-dispatch(1)
Dispatch an email to other ezmlm programs
mission-control-5(8)
Telepathy account manager/chanel dispatcher
ne_request_create(3), ne_request_dispatch(3), ne_request_destroy(3)
low-level HTTP request handling
openssl-core_dispatch.h(7), openssl/core_dispatch.h(7)
OpenSSL provider dispatch numbers and function types
pcap_breakloop(3)
force a pcap_dispatch() or pcap_loop() call to return
pcap_loop(3), pcap_dispatch(3)
process packets from a live capture or savefile
quorum_dispatch(3)
Dispatches callbacks from the quorum service
quorum_fd_get(3)
Dispatches callbacks from the quorum service
votequorum_dispatch(3)
Dispatches callbacks from the votequorum service
votequorum_fd_get(3)
Dispatches callbacks from the votequorum service
Amon2::Plugin::LogDispatch(3)
Log::Dispatch glue for Amon2
Amon2::Web::Dispatcher::Lite(3)
Sinatra like dispatcher for Amon2
Amon2::Web::Dispatcher::RouterBoom(3)
Router::Boom bindings
Amon2::Web::Dispatcher::RouterSimple(3)
Router::Simple binding for Amon2
App::CLI(3)
Dispatcher module for command line interface programs
App::Cmd::Subdispatch(3)
an App::Cmd::Command that is also an App::Cmd
App::Cmd::Subdispatch::DashedStyle(3)
"app cmd --subcmd" style subdispatching
Bread::Board::Manual::Example::LogDispatch(3)
An example of composing a dynamic Log::Dispatch object
CGI::Application::Dispatch(3)
Dispatch requests to CGI::Application based objects
CGI::Application::Dispatch::PSGI(3)
Dispatch requests to CGI::Application based objects using PSGI
CGI::Application::Dispatch::Regexp(3)
Dispatch requests to CGI::Application based objects using regular expressions
CGI::Application::Dispatch::Server(3)
A simple HTTP server for developing with CGI::Application::Dispatch
CGI::Application::Plugin::LogDispatch(3)
Add Log::Dispatch support to CGI::Application
Catalyst::Action::REST(3)
Automated REST Method Dispatching
Catalyst::Action::REST::ForBrowsers(3)
Automated REST Method Dispatching that Accommodates Browsers
Catalyst::Action::SOAP::RPCEndpoint(3)
RPC Dispatcher
Catalyst::Controller::SRU(3)
Dispatch SRU methods with Catalyst
Catalyst::DispatchType(3)
DispatchType Base Class
Catalyst::DispatchType::Chained(3)
Path Part DispatchType
Catalyst::DispatchType::Default(3)
Default DispatchType
Catalyst::DispatchType::Index(3)
Index DispatchType
Catalyst::DispatchType::LocalRegex(3)
LocalRegex DispatchType
Catalyst::DispatchType::LocalRegexp(3)
LocalRegexp DispatchType
Catalyst::DispatchType::Path(3)
Path DispatchType
Catalyst::DispatchType::Regex(3)
Regex DispatchType
Catalyst::DispatchType::Regexp(3)
Regex DispatchType
Catalyst::Dispatcher(3)
The Catalyst Dispatcher
Catalyst::Exception::Detach(3)
Exception for redispatching using $ctx->detach()
Catalyst::Exception::Go(3)
Exception for redispatching using $ctx->go()
Catalyst::Plugin::Log::Dispatch(3)
Log module of Catalyst that uses Log::Dispatch
Catalyst::Plugin::Server::XMLRPC::DispatchType::XMLRPCPath(3)
XMLRPCPath DispatchType
Catalyst::Plugin::Server::XMLRPC::DispatchType::XMLRPCRegex(3)
XMLRPCRegex DispatchType
Catalyst::Plugin::XMLRPC(3)
DEPRECATED Dispatch XMLRPC methods with Catalyst
Catalyst::Plugin::XMLRPC::DispatchType::XMLRPC(3)
XMLRPC DispatchType
Class::Forward(3)
Namespace Dispatch and Resolution
Class::MixinFactory::NEXT(3)
Superclass method redispatch for mixins
Class::Multimethods::Pure(3)
Method-ordered multimethod dispatch
Dancer2::Core::Dispatcher(3)
Class for dispatching request to the appropriate route handler
Dancer::RPCPlugin::DispatchFromConfig(3)
Build dispatch-table from the Dancer Config
Dancer::RPCPlugin::DispatchFromPod(3)
Build dispatch-table from POD
Dancer::RPCPlugin::DispatchItem(3)
Small object to handle dispatch-table items
Dancer::RPCPlugin::DispatchMethodList(3)
Class for maintaining a global methodlist
DateTime::Format::Builder::Parser::Dispatch(3)
Dispatch parsers by group
Gantry::Conf::FAQ(3)
Frequently Asked Questions regarding Gantry::Conf "Why should I use Gantry::Conf at all?" 4 Item "Why should I use Gantry::Conf at all?" There are many reasons why we feel Gantry::Conf is helpful both during development and after deployment. The next two entries should hopefully answer this question for you as they outline a few common scenarios programmers and system administrators often face. "How is Gantry::Conf helpful during development?" 4 Item "How is Gantry::Conf helpful during development?" "Easy separation of development configs from production configs" 4 Item "Easy separation of development configs from production configs" Often programmers have a separate development environment from their production environment. By using <shared> blocks and dev instances you can avoid spending any serious time setting up your application in the development environment. Take this configuration example: <shared dev> dbuser nobody dbpass secret dbconn "dbi:Pg:dbname=dev" </shared> <shared production> dbuser apache dbpass secret2 dbconn "dbi:Pg:dbname=production" </shared> <instance app1> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use production </instance> <instance app1-dev> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use dev </instance> By separating out our production and dev database information into shared blocks we can essentially switch between our production and dev environments by simply changing the instance we are using. If you were working on a script this would be a simple matter of running: $ script.pl --instance=app1-dev instead of: $ script.pl --instance=app1 "How is Gatnry::Conf helpful in production?" 4 Item "How is Gatnry::Conf helpful in production?" Gantry::Conf has several advantages in a production environment. First, it provides a single place for all config information, if you commit to it. Even if you don't commit to it for all apps, it still provides control to the installing admin over how and where conf information is stored. For instance, the admin could put the config information directly into /etc/gantry.conf, or into a separate file in /etc/gantry.d. She could even set up a secure web server where all boxes would go to get their conf. The short answer is, Gantry::Conf is flexible and production environments benefit from flexibility. "How do I pass my instance information into my application?" 4 Item "How do I pass my instance information into my application?" There are many possible ways to do this a few of which are: "Command line arguments" 4 Item "Command line arguments" If your application accepts arguments on the command line we suggest adding an --instance option to pass in the instance's name. "PerlSetVar" 4 Item "PerlSetVar" In a mod_perl environment you could use a PerlSetVar, possibly named GantryConfInstance, to pull in this value for your application. "ModPerl::ParamBuilder" 4 Item "ModPerl::ParamBuilder" Again in a mod_perl environment, another option would be to use ModPerl::ParamBuilder to pass the instance name. "Hard coded" 4 Item "Hard coded" We include this for the sake of completeness, but advise against it. You could always simply hard code your instance information into your application, but this will greatly reduce the flexibility you have. "How do I add a different provider for an existing ConfigVia method?" 4 Item "How do I add a different provider for an existing ConfigVia method?" Place your provider module in the Gantry::Conf::Provider::Method::* namespace. Make sure your public API matches the existing providers which use the same method. For instance the flat file providers all implement a config method which is called as a class method and receives a file name. "How do I add to the ConfigVia methods?" 4 Item "How do I add to the ConfigVia methods?" If none of the existing provider methods will do, you need to work in Gantry::Conf. In particular, you need to augment the dispatch hash with the name of your provisioning method and a sub name which will handle it. Then you need to implement the method you put in %dispatch
Gungho::Log::Dispatch(3)
Log::Dispatch-Based Log For Gungho
JSON::RPC::Dispatch(3)
Dispatch JSON RPC Requests To Handlers
JSON::RPC::Dispatcher(3)
A JSON-RPC 2.0 server
JSON::RPC::Dispatcher::App(3)
A base class for creating object oriented apps with JRD
JSON::RPC::Dispatcher::Procedure(3)
The data holder between RPC requests and responses
Jifty::Dispatcher(3)
The Jifty Dispatcher
Jifty::Plugin::AdminUI::Dispatcher(3)
dispatcher of the AdminUI plugin
Jifty::Plugin::Authentication::Password::Dispatcher(3)
password plugin dispatcher
Jifty::Plugin::Config::Dispatcher(3)
dispatcher of the Config plugin
Jifty::Plugin::LetMe::Dispatcher(3)
Dispatcher for LetMe plugin
Jifty::Plugin::OnlineDocs::Dispatcher(3)
Dispatcher for OnlineDocs plugin
Jifty::Plugin::REST::Dispatcher(3)
Dispatcher for REST plugin
Jifty::Plugin::SinglePage::Dispatcher(3)
Dispatcher for SinglePage plugin
Jifty::Plugin::SkeletonApp::Dispatcher(3)
Dispatcher for SkeletonApp plugin
Log::Dispatch(3)
Dispatches messages to one or more outputs
Log::Dispatch::ApacheLog(3)
Object for logging to Apache::Log objects
Log::Dispatch::Array(3)
log events to an array (reference)
Log::Dispatch::ArrayWithLimits(3)
Log to array, with some limits applied
Log::Dispatch::Base(3)
Code shared by dispatch and output objects
Log::Dispatch::Code(3)
Object for logging to a subroutine reference
Log::Dispatch::Colorful(3)
Object for logging to screen
Log::Dispatch::Config(3)
Log4j for Perl
Log::Dispatch::Configurator(3)
Abstract Configurator class
Log::Dispatch::Configurator::Any(3)
Configurator implementation with Config::Any
Log::Dispatch::Configurator::AppConfig(3)
Configurator implementation with AppConfig
Log::Dispatch::Configurator::YAML(3)
Configurator implementation with YAML
Log::Dispatch::DBI(3)
Class for logging to database via DBI interface
Log::Dispatch::Dir(3)
Log messages to separate files in a directory, with rotate options
Log::Dispatch::Email(3)
Base class for objects that send log messages via email
Log::Dispatch::Email::EmailSend(3)
Subclass of Log::Dispatch::Email that uses Email::Send
Log::Dispatch::Email::MIMELite(3)
Subclass of Log::Dispatch::Email that uses the MIME::Lite module
Log::Dispatch::Email::MailSend(3)
Subclass of Log::Dispatch::Email that uses the Mail::Send module
Log::Dispatch::Email::MailSender(3)
Subclass of Log::Dispatch::Email that uses the Mail::Sender module
Log::Dispatch::Email::MailSendmail(3)
Subclass of Log::Dispatch::Email that uses the Mail::Sendmail module
Log::Dispatch::File(3)
Object for logging to files
Log::Dispatch::File::Locked(3)
Subclass of Log::Dispatch::File to facilitate locking
Log::Dispatch::File::Rolling(3)
Object for logging to date/time/pid stamped files
Log::Dispatch::File::Stamped(3)
Logging to date/time stamped files
Log::Dispatch::FileRotate(3)
Log to Files that Archive/Rotate Themselves
Log::Dispatch::FileRotate::Flock(3)
File Locking Functions for Log::Dispatch::FileRotate
Log::Dispatch::FileRotate::Mutex(3)
Flock Based File Mutex
Log::Dispatch::FileShared(3)
Log::Dispatch output class for logging to shared files
Log::Dispatch::FileWriteRotate(3)
Log to files that archive/rotate themselves, w/ File::Write::Rotate
Log::Dispatch::Handle(3)
Object for logging to IO::Handle classes
Log::Dispatch::Null(3)
Object that accepts messages and does nothing
Log::Dispatch::Output(3)
Base class for all Log::Dispatch::* objects
Log::Dispatch::Perl(3)
Use core Perl functions for logging
Log::Dispatch::Screen(3)
Object for logging to the screen
Log::Dispatch::Screen::Color(3)
attached color for Log::Dispatch::Screen
Log::Dispatch::Scribe(3)
Logging via Facebook's Scribe server software
Log::Dispatch::Syslog(3)
Object for logging to system log
Log::Dispatch::Types(3)
Types used for parameter checking in Log::Dispatch
Log::Dispatch::Vars(3)
Variables used internally by multiple packages
Log::Dispatchouli(3)
a simple wrapper around Log::Dispatch
Log::Dispatchouli::Global(3)
a system for sharing a global, dynamically-scoped logger
Log::Dispatchouli::Proxy(3)
a simple wrapper around Log::Dispatch
Log::Log4perl::JavaMap(3)
maps java log4j appenders to Log::Dispatch classes
Log::Log4perl::JavaMap::ConsoleAppender(3)
wraps Log::Dispatch::Screen
Log::Log4perl::JavaMap::FileAppender(3)
wraps Log::Dispatch::File
Log::Log4perl::JavaMap::NTEventLogAppender(3)
wraps Log::Dispatch::Win32EventLog
Log::Log4perl::JavaMap::RollingFileAppender(3)
wraps Log::Dispatch::FileRotate
Log::Log4perl::JavaMap::SyslogAppender(3), Log::Log4perl::JavaMap::SysLogAppender(3)
wraps Log::Dispatch::Syslog
Log::Report::Dispatcher(3)
manage message dispatching, display or logging
Log::Report::Dispatcher::Callback(3)
call a code-ref for each log-line
Log::Report::Dispatcher::File(3)
send messages to a file or file-handle
Log::Report::Dispatcher::Log4perl(3)
send messages to Log::Log4perl back-end
Log::Report::Dispatcher::LogDispatch(3)
send messages to Log::Dispatch back-end
Log::Report::Dispatcher::Perl(3)
send messages to die and warn
Log::Report::Dispatcher::Syslog(3)
send messages to syslog
Log::Report::Dispatcher::Try(3)
capture all reports as exceptions
Mail::DMARC::Report::Send(3)
report sending dispatch class
Mason::Manual::RequestDispatch(3)
How request paths get mapped to page components
Mixin::Event::Dispatch(3)
mixin methods for simple event/message dispatch framework
Mixin::Event::Dispatch::Bus(3)
a message bus
Mixin::Event::Dispatch::Event(3)
an event object
Mixin::Event::Dispatch::Methods(3)
importer class for applying Mixin::Event::Dispatch methods without inheritance
Mojo::DynamicMethods(3)
Fast dynamic method dispatch
MojoMojo::Formatter::Main(3)
MojoMojo's main formatter, dispatching between Textile and MultiMarkdown
MojoX::Log::Dispatch::Simple(3)
Simple Log::Dispatch replacement of Mojo::Log
MooseX::Declare::Syntax::OptionHandling(3)
Option parser dispatching
MooseX::MultiMethods(3)
Multi Method Dispatch based on Moose type constraints
MooseX::Role::Loggable(3)
Extensive, yet simple, logging role using Log::Dispatchouli
NEXT(3)
Provide a pseudo-class NEXT (et al) that allows method redispatch
Net::Analysis::Dispatcher(3)
handle the event stuff for the proto analysers
Net::HTTP::Spore::Middleware::LogDispatch(3)
Net::HTTP::Spore::Middleware::LogDispatch is a middleware that allow you to use LogDispatch
Net::SIP::Dispatcher(3)
dispatch SIP packets between legs and endpoint
Net::SIP::Dispatcher::Eventloop(3)
simple event loop for Net::SIP::Dispatcher
Nginx::Simple::Dispatch(3)
Easy to use dispatcher interface for "--with-http_perl_module"
Nginx::Simple::Dispatcher::Attributes(3)
Attributes: Index, Page
POE::Session::MultiDispatch(3)
Callback dispatch for session events
Path::Dispatcher(3)
Flexible and extensible dispatch
Path::Dispatcher::Cookbook(3)
A cookbook for Path::Dispatcher
Path::Dispatcher::Declarative(3)
sugary dispatcher
Path::Dispatcher::Dispatch(3)
a list of matches
Path::Dispatcher::Match(3)
the result of a successful rule match
Path::Dispatcher::Path(3)
path and some optional metadata
Path::Dispatcher::Role::Rules(3)
"has a list of rules"
Path::Dispatcher::Rule(3)
predicate and codeblock
Path::Dispatcher::Rule::Alternation(3)
any rule must match
Path::Dispatcher::Rule::Always(3)
always matches
Path::Dispatcher::Rule::Chain(3)
Chain rules for Path::Dispatcher
Path::Dispatcher::Rule::CodeRef(3)
predicate is any subroutine
Path::Dispatcher::Rule::Dispatch(3)
redispatch
Path::Dispatcher::Rule::Empty(3)
matches only the empty path
Path::Dispatcher::Rule::Enum(3)
one of a list of strings must match
Path::Dispatcher::Rule::Eq(3)
predicate is a string equality
Path::Dispatcher::Rule::Intersection(3)
all rules must match
Path::Dispatcher::Rule::Metadata(3)
match path's metadata
Path::Dispatcher::Rule::Regex(3)
predicate is a regular expression
Path::Dispatcher::Rule::Sequence(3)
a sequence of rules
Path::Dispatcher::Rule::Tokens(3)
predicate is a list of tokens
Path::Dispatcher::Rule::Under(3)
rules under a predicate
Pipeline::Dispatch(3)
dispatcher for pipeline segments
Plack::Middleware::LogDispatch(3)
Uses Log::Dispatch to configure logger
STF::Dispatcher::Impl::File(3)
STF Storage to store data in file
STF::Dispatcher::Impl::Hash(3)
STF Storage to store data in hash
STF::Dispatcher::PSGI(3)
Pluggable STF Dispatcher Interface
STF::Dispatcher::PSGI::HTTPException(3)
Very Light Exception For STF Dispatcher
STF::Dispatcher::Test(3)
Basic Tests For STF Implementations
SUPER(3)
control superclass method dispatch
SVK::Command(3)
Base class and dispatcher for SVK commands
Servlet::RequestDispatcher(3)
request dispatcher interface
Sub::Multi(3)
Data::Bind-based multi-sub dispatch
Sub::Signatures(3)
Use proper signatures for subroutines, including dispatching
Test::Mock::LWP::Dispatch(3)
mocks LWP::UserAgent and dispatches your requests/responses
TheSchwartz::Simple(3)
Lightweight TheSchwartz job dispatcher using plain DBI
VM::EC2::Dispatch(3)
Create Perl objects from AWS XML requests
Web::Dispatch::HTTPMethods(3)
Helpers to make RESTFul Dispatchers Easier
WebService::GData::Collection(3)
Composite class redispatching method calls to query the items data
dnscheck-dispatcher(1)
daemon program to run tests from a database queue
remrt(1)
network distributed (remote) ray-trace dispatcher
snmpa_mpd(3)
Message Processing and Dispatch module for the SNMP agent
snmpm_mpd(3)
Message Processing and Dispatch module for the SNMP manager
home | help