perl - http::proxy module engine -


i have question cpan module http://search.cpan.org/dist/http-proxy/

it seems module support engines

could explain me difference between:

    use http::proxy;     $proxy = http::proxy->new( engine => 'nofork' ); 

and :

    use http::proxy;     $proxy = http::proxy->new; 

and:

   use http::proxy;    $proxy = http::proxy->new( engine => scoreboard ); 

to quote http::proxy::engine pod

the role of engine implement main fork+serve loop required bookkeeping. way test various implementation and/or try out new algorithms without difficulties.

the descriptions of various engines are:

http::proxy::engine::legacy - "older" http::proxy engine
http::proxy::engine::nofork - basic, non forking http::proxy engine
http::proxy::engine::scoreboard -a scoreboard-based http::proxy engine

note: last 1 seems implementing "scoreboard" dynamic scheduling algorithm (which used cpu instruction sceduling). in case it's more simplified, , scoreboard - glancing @ source - appears list of statuses of each forked off child process


Comments

Popular posts from this blog

java - SNMP4J General Variable Binding Error -

windows - Python Service Installation - "Could not find PythonClass entry" -

Determine if a XmlNode is empty or null in C#? -