Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

jifty::plugin::requestinspector(3pm) [debian man page]

Jifty::Plugin::RequestInspector(3pm)			User Contributed Perl Documentation		      Jifty::Plugin::RequestInspector(3pm)

NAME
Jifty::Plugin::RequestInspector - Inspect requests DESCRIPTION
Do not use this plugin directly. Other plugins use this plugin. METHODS
init Sets up hooks into the request cycle. before_request Hooks into the request cycle to forward "request is beginning" and more metadata to RequestInspector plugins. after_request Hooks into the request cycle to forward "request is done" and more metadata to RequestInspector plugins. clear_requests Clears the list of request inspections. add_request Adds the current request inspection to the data store. last_id Returns the most recent request ID. get_plugin_data RequestID, Plugin::Name Returns the opaque plugin data for a particular request ID and plugin class name. get_all_plugin_data Plugin::Name Returns the opaque plugin data for all requests, for a given plugin class name. get_request RequestID Returns all data for a particular request ID. requests Returns a list of all inspections for all requests. inspector_plugins Returns a list of plugin instances that hook into RequestInspector. new_request_inspection Instantiates a new request inspection, setting up some default values. should_handle_request CGI Decides whether the request described by the CGI parameter should be handled, based on plugin configuration. version This plugin is versioned because it provides model classes. perl v5.14.2 2010-12-08 Jifty::Plugin::RequestInspector(3pm)

Check Out this Related Man Page

Jifty::Plugin::TestServerWarnings(3pm)			User Contributed Perl Documentation		    Jifty::Plugin::TestServerWarnings(3pm)

NAME
Jifty::Plugin::TestServerWarnings - Stores server warnings away for later fetching SYNOPSIS
# In your jifty config.yml under the framework section: Plugins: - TestServerWarnings: clear_screen: 1 DESCRIPTION
This plugin add a new appender Jifty::Plugin::TestServerWarnings::Appender on the first request it sees, which stores away all messages it receives. It also removes the default "Screen" appender unless clear_screen in config.yml is set to be false or env TEST_VERBOSE is true. The warnings can be retrieved by a client-side process by calling "decoded_warnings" with a base URI to the server. This plugin is automatically added for all jifty tests. METHODS
init set clear_screen to 1 if the clear_screen in config.yml is set to be true, if it's not set at all, set it to 1 if TEST_VERBOSE is set to be true. new_request On the first call to new_request, the plugin adjusts the appenders. This causes it to only have effect if it is run in a forked server process, not in a test process. If "TEST_VERBOSE" is set, it does not remove the Screen appender. add_warnings WARN, WARN, .. Takes the given warnings, and stores them away for later reporting. stashed_warnings Returns the stored warnings, as a list. This does not clear the list, unlike "encoded_warnings" or "decoded_warnings". encoded_warnings Returns the stored warnings, encoded using Storable. This also clears the list of stashed warnings. decoded_warnings URI Given the URI to a jifty server with this plugin enabled, retrieves and decodes the stored warnings, returning them. This will also clear the server's stored list of warnings. perl v5.14.2 2010-09-25 Jifty::Plugin::TestServerWarnings(3pm)
Man Page

2 More Discussions You Might Find Interesting

1. IP Networking

Partial Request are coming... please help

Hi All, We are having the system, where we are using the socket programming (TCP/IP), a system called plugin playing a role in between two system, where its getting the request from system1 and its processing it and re-directing the request after its validation, to system2. Normally,... (0 Replies)
Discussion started by: pa.chidhambaram
0 Replies

2. Programming

Eclipse plugin to create class diagrams

Hi Guys, I wonder if anyone is aware of a eclipse plugin that I can use to create class diagrams. Thanks!!. (1 Reply)
Discussion started by: arizah
1 Replies