Free started unicast maintenance ranging no response received software for linux

Maintenance for Plone provides a set of scheduled scripts for routine work in a Plone site.
PloneMaintenance consists of a portal_maintenance tool that allows you to define maintenance tasks and scripts to run according to a schedule assigned to the tasks.
No task is going to be run unless it is scheduled to. The schedule information is stored in the task, and even if PloneMaintenance is called many times in a row, it will always look up the schedule information, check when was the last time the task was run, calculate the next time the task is scheduled to run, and depending on this, PloneMaintenance will decide whether it runs the script associated to the task or not.
PloneMaintenance depends on an external tool to wake it up and make it execute the scheduled tasks. Without an external tool, PloneMaintenance will just sit and wait, doing nothing. You can go to the portal_maintenance tool and manually run the maintenance tasks, but most of the time, you want an external tool doing the job automatically.
You can choose one of the Schedulers which are available for Zope, or call PloneMaintenance from a cron job.
Enhancements:
- Fix bug on MaintenanceTask: id was not initialized
- Add "notified_emails" property. When a task has been processed, an email is sent.
- MaintenanceTask no more addable types 2006/07/06 MR

skipjackResponse project checks Skipjack Payment gateway Response.

The SkipjackResponse Check class checks and validates the response sent via POST methods by the Skipjack payment gateway. In account setup, you need to make sure you have set response file to custom filename.

What is SkipJack?

Skipjack is another payment gateway that accepts payments online. But this payment gateway accepts payment for business in USA only.

What does my class do!

skipjackResponse class check the response that skipjack server send via POST method.

NOTE: In the preference of Skipjack account you will have to set response files.

ZOOM::IRSpy::Maintenance is a maintenance documentation for IRSpy.
The IRSpy application is implemented by five components:
- A library of classes within the ZOOM::IRSpy "namespace".
- A command-line invocation script called irspy
- A web-based UI - either this or the command-line script can be used to run the spy software, but the latter is more capable in that it also provides ways to interrogate the database of results.
- A small additional library, ZOOM::Pod, which is used by IRSpy and which is more conveniently included in this distribution than released and maintained separately.
- The configuration for a Zebra database that stores the harvested information.
These components are discussed in turn.

Net::Google::Response is a simple OOP-ish interface to the Google SOAP API search responses.

SYNOPSIS

my $service = Net::Google->new(key=>LOCAL_GOOGLE_KEY);
my $session = $service->search();

$session->query(qw(Perl modules));

# You are probably better off calling
# $session->results() but if you want
# the raw response object(s) here ya go :

my $responses = $session->response();
my $count = scalar(@$responses);

# $r is a Net::Google::Response object

foreach my $r (@$responses) {
print sprintf("%s : %sn",$r->searchQuery(),$r->estimatedTotalResults());
}

Provides a simple OOP-ish interface to the Google SOAP API for searching. This package is used by Net::Google.

The Net::Google::Response object is used to contain response information provided by the Google search service in response to a search query. The Response object allows the client program to easily access the data returned from a search.

Response data is accessed using methods with identical names to the elements of a search response (as documented in the Google Web APIs Reference, section 3). For instance, the first example in the SYNOPSIS section, above, would return the estimated number of total results for the query.

Response objects may contain other response objects, where an element would return an array of other elements. For instance, calling $response->resultElements() will return a reference to an array of Net::Google::Response objects, each one representing one result from the search.

The Response module will automatically provide methods for the search response, as described by the service WSDL file. The results format is described by the Google APIs documentation, to which you should refer for the most up-to-date information. As of the April 8th, 2002 release of the Google APIs, the methods below are provided for each search result.

Net::Gopher::Response::XML is a Perl module Convert a Gopher/Gopher+ response to XML.

SYNOPSIS

use Net::Gopher;
use Net::Gopher::Response::XML;

...

$response->as_xml(File => menu.xml);

This module contains code to convert a response from a Gopher or Gopher+ Gopherspace to XML. This functionality was originally in the Net::Gopher core, but its features are seldom needed, and it was deemed by me, Will, to be unnecessary bloat.

The module has one method, as_xml(), which you can call on Net::Gopher::Response objects to generate XML. If you have existing code that expects Net::Gopher::Response to already have as_xml() in it, just add the use Net::Gopher::Response::XML to the top of the script as shown in the SYNOPSIS and it should work fine with both pre 1.05 and post 1.05 versions.

Progress Report Manager project is a system for entering and sending school progress reports for teachers and parents.
The Progress Report Manager was built to alleviate problems experienced with traditional school progress reports.
Administrators create progress reports that are automatically sent via email.
Every week, teachers receive a message in their inbox reminding them that a new progress report has been created.
The teacher completes the progress reports online using a Web browser.
At the end of the week, the administrators click a button which sends email messages to every parent whose child received a report.
The parents can look at their students progress online and reply to teacher comments using response features.
Enhancements:
- inactivate students fixed
- help files fixed / modified / written
- report views fixed
- log files can be flushed
- semesters fixed

Apache2::RequestRec is a Perl API for Apache request record accessors.

Synopsis

use Apache2::RequestRec ();

# set supported by the handler HTTP methods
$allowed = $r->allowed();

# auth type
$auth_type = $r->ap_auth_type();

# QUERY_STRING
$args = $r->args();

# non-parsed-headers handler
$status = $r->assbackwards();

# how many bytes were sent
$bytes_sent = $r->bytes_sent();

# client connection record
$c = $r->connection();

# "Content-Encoding" HTTP response header
$r->content_encoding("gzip");

# the languages of the content
$languages = $r->content_languages();

# "Content-Encoding" HTTP response header
$r->content_type(text/plain);

# special response headers table
$err_headers_out = $r->err_headers_out();

# request mapped filename
$filename = $r->filename();

# request finfo
$finfo = $r->finfo();

# SetHandler perl-script equivalent
$r->handler(perl-script);

# was it a HEAD request?
$status = $r->header_only();

# request input headers table
$headers_in = $r->headers_in();

# request output headers table
$headers_out = $r->headers_out();

# hostname
$hostname = $r->hostname();

# input filters stack
$input_filters = $r->input_filters();

# get the main request obj in a sub-request
$main_r = $r->main();

# whats the current request (GET/POST/etc)?
$method = $r->method();

# whats the current method number?
$methnum = $r->method_number();

# current resource last modified time
$mtime = $r->mtime();

# next request object (in redirect)
$next_r = $r->next();

# there is no local copy
$r->no_local_copy();

# Apache ascii notes table
$notes = $r->notes();

# output filters stack
$output_filters = $r->output_filters();

# PATH_INFO
$path_info = $r->path_info();

# used in configuration directives modules
$per_dir_config = $r->per_dir_config();

# pool with life span of the current request
$p = $r->pool();

# previous request object in the internal redirect
$prev_r = $r->prev();

# connection level input filters stack
$proto_input_filters = $r->proto_input_filters();

# HTTP protocol version number
$proto_num = $r->proto_num();

# connection level output filters stack
$proto_output_filters = $r->proto_output_filters();

# the protocol, the client speaks: "HTTP/1.0", "HTTP/1.1", etc.
$protocol = $r->protocol();

# is it a proxy request
$status = $r->proxyreq($val);

# Time when the request started
$request_time = $r->request_time();

# server object
$s = $r->server();

# response status
$status = $r->status();

# response status line
$status_line = $r->status_line();

# manipulate %ENV of the subprocess
$r->subprocess_env;
$r->subprocess_env($key => $val);

# first HTTP request header
$request = $r->the_request();

# the URI without any parsing performed
$unparsed_uri = $r->unparsed_uri();

# The path portion of the URI
$uri = $r->uri();

# auth username
$user = $r->user();