Free in response software for linux

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.

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.

Reliable Response Notification provides guaranteed delivery of critical messages to a wide range of devices. The project guarantees that every emergency will have one, and only one, person responding and taking charge of the recovery.
For integrated services, like some network monitors, help-desk packages, and security suites, Reliable Response Notification allows the user to update records via their mobile devices. It is available as either a standalone server or as a hosted service.
Enhancements:
- The product supports three types of groups: broadcast, escalation and on-call.
- Many devices are supported, including email, SMS, text-to-speech, Jabber, GTalk, SameTime IM, and alphanumeric pagers.
- Integrations for a number of packages are available.
- There is an easy system to add new integrations as needed.

WWW::Patent::Page::Response is an object holding a patent page or document (e.g. htm, pdf, tif) from selected source (e.g. from United States Patent and Trademark Office (USPTO) website or the European Patent Office (ESPACE_EP), as constructed by WWW::Patent::Page, in passing analogy to LWP::UserAgent and HTTP::Response.

SYNOPSIS

Please see the test suite for working examples. The following is not guaranteed to be working or up-to-date.

$ perl -I. -MWWW::Patent::Page -e print $WWW::Patent::Page::VERSION,"n"
0.02

use WWW::Patent::Page;

print $WWW::Patent::Page::VERSION,"n";

my $patent_browser = WWW::Patent::Page->new(); # new object

my $document1 = $patent_document->get(6,123,456);
# defaults:
# office => ESPACE_EP,
# country => US,
# format => pdf,
# page => all,
# and usual defaults of LWP::UserAgent (subclassed)

my $document2 = $patent_document->provide_doc(US6123456,
office => ESPACE_EP ,
format => pdf,
page => 2 ,
);

my $pages_known = $patent_document->pages_available( # e.g. TIFF
document=> 6123456,
);

Intent: Use public sources to retrieve patent documents such as TIFF images of patent pages, html of patents, pdf, etc. Expandable for your office of interest by writing new submodules..

MySpace Friend Renamer provides an extension that allows you to rename your MySpace Friends.

This adds a right click option to Myspace Pages and allows you to change the display name for any of your friends. Handy if your friends change names often, or pick strange and obscure names.

Also in response to comments. If a tab is not in focus when the page loads, the extension will not rename.

I believe that the extension will conflict with other extensions that change pages when they load. If I find a better way to do it, I will change it.

PagePoker is a Perl package that defines a browser agent with many powerful features for monitoring and testing Web sites, including elaborate failure handling that can send email and trigger SNMP traps. The application comes with three scripts that implement it for different uses: poke.pl, for single agents; pokes.pl, for many parallel agents, and pokehard.pl, for loadtesting and benchmarking.

HOW-TO:

Run "poke.pl --help" for detailed help on using the package. Briefly, poke.pl creates a PagePoker object, accepting all sorts of options. It is designed for monitoring web pages to verify they are returning desired information or to dump the contents of web pages to a file (like fetch). It can loop on a variety of conditions and crawl a series of pages, posting and passing cookies. The other component, pokes.pl, is simply a forking variation that accepts as its parameters an agent id and the options for that agent. It can be used for monitoring many sites simultaneously or for load testing single sites. On a dual 400 mhz machine I was able to run about 120 concurrent agents.

Examples:

> poke.pl --url http://node.to

returns (first element is date):
20000225170507 SUCCESS: Page loaded by agent

> poke.pl --url http://node.to --no-status --print-response

returns the plain html

> pokes.pl agent1 "--url http://node.to --no-status --email-failures
--email-address who@node.to --iterations 1000 --interval 10"
agent2 "--urls http://node.to>>http://tiny.node.to
--no-status --email-failures --email-address "1@1.com 2@2.com""

will launch two agents, first agent will poll node.to for connection failures every 10 seconds 1000 times, emailing if a failure is encountered, second agent will hit node.to then tiny.node.to and exit, emailing two people if either one doesnt respond.

There is a lot of logic to control how often and under what conditions email is sent. You can search for desired in text the headers or the html response, and send email or snmp traps on certain failure conditions. To loadtest, you could launch looping batches of ten agents, adding ten more a minute later in a another process, etc.

More advanced load testing can be done with pokehard.pl. It gets its own README (README.pokehard).

Here is the output of poke.pl --help, minus the USAGE statement:

How to use it:

--url "http://host/page"

--urls "http://host/page1>>http://host/page2>>etc"

--urls-from-file "file_path"

--urls-delay "n"
Seconds between each request

--method {GET|POST}

--post-query "query string"

--basic-auth-name "agent login" (one per agent)

--basic-auth-pass "agent password"

--interval "n"
Loop with n seconds between pokes

--iterations "n"
Cycles to run loop (requires --interval)

--look-for "pattern to find in response text"

--resend-cookie "cookiename"

--resend-cookie-between-iterations
Allow cookie to be resent through all iterations

--use-verbose-response
Includes headers in response text

--print-response
Dump agent retrieved text to STDOUT

--disable-on-failure
Allow server disabling on failure

--disable-snmp-trap "snmp trap"
To disable in loadbalancer

--enable-on-recovery
Allow server re-enabling on recovery

--enable-snmp-trap "snmp trap"
To enable server after successful run

--email-failures
Turn on alarm emails

--email-addresses "address1 address2 etc"

--email-subject "override default with arbitrary text"

--failures-until-email "n"
Consecutive errors triggers email

--min-time-between-emails "seconds"

--die-after-date "yyyymmddhhmmss" (requires interval and iterations)

--benchmark
Store numbers used for performance measurement (by pokehard.pl)

--quiet
Output nothing (except email, if set)

--no-status
Do not output status info (ie SUCCESS, etc)

--print-to-file "file"
Write output to file

--help
Print this text and exit

The Ming Server generates Web pages statically or dynamically. As a local executable, it generates a static site from a directory tree of simple text files.
Installed in cgi-bin, it creates those same pages on demand in response to browser requests. Parsing of different source types, the creation, and the writing of pages are separated, making it easy to extend The Ming Server to new data types or delivery methods.
Enhancements:
- A bug in Logger was fixed along with a problem in ming.cgi.