Free requests software for linux

Requirements:

• Python
• Beanstalkd server

WebChat2aim is a server that will connect/disconnect your AIM bot. It provides a bridge API to connect your Web visitors to your AIM API.

The script allows your Web site to broadcast and then allow a CSR to answer the incoming requests. Your Web site uses curl et al to command and control the actual persistent AIM connection.

CPPSERV is an application server that provides Servlet-like API to C++ programmers.

CPPSERV project consists of stand-alone daemon, listening on TCP socket for requests from web server, and web server module.

Currently only apache-2.0.x is supported, but writing modules for other web servers should be fairly easy.

httping is a "ping"-like tool for HTTP requests. Give it a URL and it will show how long it takes to connect, send a request, and retrieve the reply (only the headers).
httping can be used for monitoring or statistical purposes (measuring latency).
Enhancements:
- A big memory leak in the SSL code was fixed.
- An audible ping mode was added.

POE::Stage is a base Perl class for message-driven objects.

SYNOPSIS

#!/usr/bin/env perl
{
package App;
use POE::Stage::App qw(:base);
sub on_run {
print "hello, ", my $arg_whom, "!n";
}
}
App->new()->run( whom => "world" );
exit;

POE::Stage is a set of base classes for message-driven objects. It cleanly implements standard patterns that have emerged from years of working with POE and POE::Component modules.

As I hope the name implies, POE::Stage objects encapsulate discrete steps, or stages, of a larger task. Eventually they come together to implement programs.
For example, HTTP requests are performed in four or so distinct stages: 1. The servers address is resolved. 2. The client establishes a connection to the server. 3. The client transmits a request. 4. The client receives a response.

By design, POE::Stage promotes the decomposition of tasks into multiple, smaller stages. If these stages are generic enough, new tasks may be handled by reusing them in different configurations.

The hypothetical HTTP client might be a single stage composed of three smaller ones: A DNS resolver stage, which accepts DNS requests and returns DNS responses. A TCP client connection factory, which takes socket endpoint descriptions and other parameters, and eventually returns established connections. Finally, there would be an HTTP protocol stage that uses established connections to send requests and parse responses.

These stages would be encapsulated by a higher-level HTTP client stage. This would accept HTTP requests and return HTTP responses after performing the necessary steps to gather them.

This will sound familiar to anyone working with objects.

These objects are asynchronous and message-driven, however. The base message class, POE::Request, and its subclasses, implement a standard request/response interface between POE::Stage objects. Where possible, these messages attempt to mimic simpler, more direct call/return syntax, albeit asynchronously. POE::Stage also provides a powerful closure-based system for maintaining request and response state, so you dont have to.

python-gammu are Python bindings for Gammu library. It currently does not support all Gammu features, but range of covered functions is increasing, if you need some specific, feel free to use bug tracking system for feature requests.

YAZ Proxy application is highly configurable and can be used in a number of different applications, ranging from debugging Z39.50-based applications and protecting overworked servers, to improving the performance of stateless WWW/Z39.50 gateways.
Main features:
- Configurable logging
- SRU/SRW server function, to allow any Z39.50 server to also support the ZiNG protocols
- Load balancing across multiple backend servers
- Session-sharing and pre-initialization to improve performance in servers with expensive session initialization
- Configurable request filtering, to keep bad requests from reaching the server
- XML support -- MARC records can be converted to MARCXML, and XSLT-transformations allow the proxy to support arbitrary retrieval schemas in XML
- Load governor function limits requests from aggressive batch-mode clients
- Efficient multiplexing software enables small memory footprint and very high performance
NOTE: The YAZ Proxy, a complete application, is available under the GPL license. Other licensing terms are available to commercial vendors upon request.