www.LinuxHowtos.org howtos, tips&tricks and tutorials for linux

from small one page howto to huge articles all in one place

Other .linuxhowtos.org sites:toolsntoys.linuxhowtos.org
gentoo.linuxhowtos.org

poll results

Last additions:

using iotop to find disk usage hogs

words:

887

views:

20251

userrating:

average rating: 3.4 (205 votes) (1=very good 6=terrible)

May 25th. 2007:

Words

486

Views

36026

why adblockers are bad

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

20991

userrating:

average rating: 1.0 (50 votes) (1=very good 6=terrible)

April, 26th. 2006:

Words

Views

16061

New subdomain: toolsntoys.linuxhowtos.org

You are here: manpages

HTTP::Proxy::Engine

Section: User Contributed Perl Documentation (3)
Updated: 2010-03-30
Index Return to Main Contents

NAME

HTTP::Proxy::Engine - Generic child process manager engine for HTTP::Proxy

SYNOPSIS

    use HTTP::Proxy;

    # use the default engine for your system
    my $proxy = HTTP::Proxy->new();

    # choose one
    my $proxy = HTTP::Proxy->new( engine => 'Old' );

DESCRIPTION

The HTTP::Proxy::Engine class is a front-end to actual proxy engine classes.

The role of an engine is to implement the main fork+serve loop with all the required bookkeeping. This is also a good way to test various implementation and/or try out new algorithms without too much difficulties.

METHODS

new(): Create a new engine. The parameter "engine" is used to decide which kind of engine will be created. Other parameters are passed to the underlying engine.
This method also implement the subclasses constructor (they obviously do not need the "engine" parameter).

CREATING YOUR OWN ENGINE

It is possible to create one's own engine, by creating a simple subclass of HTTP::Proxy::Engine with the following methods:

start()

This method should handle any initialisation required when the engine starts.

run()

This method is the main loop of the master process. It defines how child processes are forked, checked and killed.

The engine MUST have a run() method, and it will be called again and again until the proxy exits.

$self->proxy->daemon returns the listening socket that can accept() connections. The child must call $self->proxy->serve_connections() on the returned socket to handle actual TCP connections.

stop()

This optional method should handle any cleanup procedures when the engine stops (typically when the main proxy process is killed).

A subclass may also define a %defaults hash (with "our") that contains the default values for the fields used internaly.

METHODS PROVIDED TO SUBCLASSES

HTTP::Proxy::Engine provides the following methods to its subclasses:

proxy(): Return the HTTP::Proxy object that runs the engine.
max_clients(): Get or set the maximum number of TCP clients, that is to say the maximum number of forked child process.
Some engines may understand a value of 0 as do not fork at all. This is what HTTP::Proxy::Engine::Legacy does.
make_accessors( @names ): Create accessors named after @names in the subclass package. All accessors are read/write. This is a utility method.
This is a class method.