Free ezweb 0.26 software for linux

HTTP::MobileAgent::EZweb is a EZweb implementation.

SYNOPSIS

use HTTP::MobileAgent;

local $ENV{HTTP_USER_AGENT} = "UP.Browser/3.01-HI02 UP.Link/3.2.1.2";
my $agent = HTTP::MobileAgent->new;

printf "Name: %sn", $agent->name; # "UP.Browser"
printf "Version: %sn", $agent->version; # 3.01
printf "DevieID: %sn", $agent->device_id; # HI02
printf "Server: %sn", $agent->server; # "UP.Link/3.2.1.2"

# e.g.) UP.Browser/3.01-HI02 UP.Link/3.2.1.2 (Google WAP Proxy/1.0)
printf "Comment: %sn", $agent->comment; # "Google WAP Proxy/1.0"

# e.g.) KDDI-TS21 UP.Browser/6.0.2.276 (GUI) MMP/1.1
print "XHTML compiant!n" if $agent->xhtml_compliant; # true

HTTP::MobileAgent::EZweb is a subclass of HTTP::MobileAgent, which implements EZweb (WAP1.0/2.0) user agents.

Shake project is a defragmenter that runs in userspace, without the need of patching the kernel and while the systems is used.
There is nothing magic in that : it just works by rewriting fragmented files. But it has some heuristics that could make it more efficient than other tools, including defrag and, maybe, xfs_fsr.
As root, call shake my_dir, and go do something usefull or pleasant until it complete. Then my_dir should be less fragmented.
For better results, you should call Shake on the whole partition, when youre not using it.
If you just wanted to see the fragmentation, call shake --pretend --verbose --verbose my_dir, alias shake -pvv my_dir.
Enhancements:
- A PPC target was added to the ebuild.
- A workaround for a reiser4 bug was added.
- Copyright notices and some comments were corrected.

neon is an HTTP and WebDAV client library for Unix systems, with a C language API. neon project provides high-level interfaces to HTTP/1.1 and WebDAV methods, and a low-level interface to HTTP request/response handling, allowing new methods to be easily implemented.
Main features:
- High-level interface to HTTP and WebDAV methods (PUT, GET, HEAD etc)
- Low-level interface to HTTP request handling, to allow implementing new methods easily.
- persistent connections
- RFC2617 basic and digest authentication (including auth-int, md5-sess)
- Proxy support (including basic/digest authentication)
- SSL/TLS support using OpenSSL (including client certificate support)
- Generic WebDAV 207 XML response handling mechanism
- XML parsing using the expat or libxml parsers
- Easy generation of error messages from 207 error responses
- WebDAV resource manipulation: MOVE, COPY, DELETE, MKCOL.
- WebDAV metadata support: set and remove properties, query any set of properties (PROPPATCH/PROPFIND).
- autoconf macros supplied for easily embedding neon directly inside an application source tree.
Enhancements:
- This release includes a number of bugfixes, particularly to the authentication code.

Test::Tech is a Perl module that adds skip_tests and test data structures capabilities to the "Test" module.

SYNOPSIS

#######
# Procedural (subroutine) Interface
#
# (use for &Test::plan, &Test::ok, &Test::skip drop in)
#
use Test::Tech qw(demo finish is_skip ok ok_sub plan skip skip_sub
skip_tests stringify tech_config);

demo($quoted_expression, @expression);

(@stats) = finish( );
$num_passed = finish( );

$skip_on = is_skip( );
($skip_on, $skip_diag) = is_skip( );

$test_ok = ok($actual_results, $expected_results, [@options]);
$test_ok = ok($actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = ok($actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = ok_sub(⊂routine, $actual_results, $expected_results, [@options]);
$test_ok = ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$success = plan(@args);

$test_ok = skip($skip_test, $actual_results, $expected_results, [@options]);
$test_ok = skip($skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = skip($skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, [@options]);
$test_ok = skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$skip_on = skip_tests( $on_off, $skip_diagnostic);
$skip_on = skip_tests( $on_off );
$skip_on = skip_tests( );

$string = stringify($var, @options); # imported from Data::Secs2

$new_value = tech_config( $key, $old_value);

#####
# Object Interface
#
$tech = new Test::Tech;

$tech->demo($quoted_expression, @expression)

(@stats) = $tech->finish( );
$num_passed = $tech->finish( );

$skip_on = $tech->is_skip( );
($skip_on, $skip_diag) = $tech->is_skip( );

$test_ok = $tech->ok($actual_results, $expected_results, [@options]);
$test_ok = $tech->ok($actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->ok($actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = $tech->ok_sub(⊂routine, $actual_results, $expected_results, [@options]);
$test_ok = $tech->ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$success = $tech->plan(@args);

$test_ok = $tech->skip($skip_test, $actual_results, $expected_results, [@options]);
$test_ok = $tech->skip($skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->skip($skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = $tech->skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, [@options]);
$test_ok = $tech->skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$state = $tech->skip_tests( );
$state = $tech->skip_tests( $on_off );

$state = skip_tests( $on_off, $skip_diagnostic );

$string = $tech->stringify($var, @options); # imported from Data::Secs2

$new_value = $tech->tech_config($key, $old_value);

Generally, if a subroutine will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}. If a subroutine will process an array reference, @options, [@options], that subroutine will also process a hash reference, %options, {@options}. See the description for a subroutine for details and exceptions.

FSA::Rules is a Perl module to build simple rules-based state machines in Perl.

Synopsis

my $fsa = FSA::Rules->new(
ping => {
do => sub {
print "ping!n";
my $state = shift;
$state->result(pong);
$state->machine->{count}++;
},
rules => [
game_over => sub { shift->machine->{count} >= 20 },
pong => sub { shift->result eq pong },
],
},

pong => {
do => sub { print "pong!n" },
rules => [ ping => 1, ], # always goes back to ping
},
game_over => { do => sub { print "Game Overn" } }
);

$fsa->start;
$fsa->switch until $fsa->at(game_over);

This class implements a simple state machine pattern, allowing you to quickly build rules-based state machines in Perl. As a simple implementation of a powerful concept, it differs slightly from an ideal DFA model in that it does not enforce a single possible switch from one state to another. Rather, it short circuits the evaluation of the rules for such switches, so that the first rule to return a true value will trigger its switch and no other switch rules will be checked. (But see the strict attribute and parameter to new().) It differs from an NFA model in that it offers no back-tracking. But in truth, you can use it to build a state machine that adheres to either model--hence the more generic FSA moniker.

FSA::Rules uses named states so that its easy to tell what state youre in and what state you want to go to. Each state may optionally define actions that are triggered upon entering the state, after entering the state, and upon exiting the state. They may also define rules for switching to other states, and these rules may specify the execution of switch-specific actions. All actions are defined in terms of anonymous subroutines that should expect an FSA::State object itself to be passed as the sole argument.

FSA::Rules objects and the FSA::State objects that make them up are all implemented as empty hash references. This design allows the action subroutines to use the FSA::State object passed as the sole argument, as well as the FSA::Rules object available via its machine() method, to stash data for other states to access, without the possibility of interfering with the state or the state machine itself.

PHP::Session is a Perl module to read / write PHP session files.

SYNOPSIS

use PHP::Session;

my $session = PHP::Session->new($id);

# session id
my $id = $session->id;

# get/set session data
my $foo = $session->get(foo);
$session->set(bar => $bar);

# remove session data
$session->unregister(foo);

# remove all session data
$session->unset;

# check if data is registered
$session->is_registered(bar);

# save session data
$session->save;

# destroy session
$session->destroy;

# create session file, if not existent
$session = PHP::Session->new($new_sid, { create => 1 });

PHP::Session provides a way to read / write PHP4 session files, with which you can make your Perl application session shared with PHP4.

If you like Apache::Session interface for session management, there is a glue for Apache::Session of this module, Apache::Session::PHP.

Devel::Cover package contains code coverage metrics for Perl.

SYNOPSIS

perl -MDevel::Cover yourprog args
cover

perl -MDevel::Cover=-db,cover_db,-coverage,statement,time yourprog args
To test an uninstalled module:
cover -delete
HARNESS_PERL_SWITCHES=-MDevel::Cover make test
cover
To test an uninstalled module which uses Module::Build (0.26 or later):
./Build testcover
If the module does not use the t/*.t framework:
PERL5OPT=-MDevel::Cover make test

This module provides code coverage metrics for Perl. Code coverage metrics describe how throroughly tests exercise code. By using Devel::Cover you can find areas of code not exercised by your tests and find out which tests to create to increase coverage. Code coverage can be considered as an indirect measure of quality.

If you cant guess by the version number this is an alpha release.
Code coverage data are collected using a pluggable runops function which counts how many times each op is executed. These data are then mapped back to reality using the B compiler modules. There is also a statement profiling facility which needs a better backend to be really useful.

The cover program can be used to generate coverage reports.

Statement, branch, condition, subroutine, pod and time coverage information is reported. Statement coverage data should be reasonable, although there may be some statements which are not reported. Branch and condition coverage data should be mostly accurate too, although not always what one might initially expect. Subroutine coverage should be as accurate as statement coverage. Pod coverage comes from Pod::Coverage. If Pod::Coverage::CountParents is available it will be used instead. Coverage data for path coverage are not yet collected.

The gcov2perl program can be used to convert gcov files to Devel::Cover databases.

You may find that the results dont match your expectations. I would imagine that at least one of them is wrong.

The most appropriate mailing list on which to discuss this module would be perl-qa. Discussion has migrated there from perl-qa-metrics which is now defunct. See http://lists.perl.org/showlist.cgi?name=perl-qa.

mod_authz_ldap is an Apache LDAP Authorization module.
What it does:
This Apache LDAP authentication/authorization module tries to solve the following problems that other such modules may not solve in all cases:
- Map the short form of the distinguished name of a certificate and its issuer obtained from the environment of mod_ssl to a user distinguished name in an LDAP directory.
- Check the age of a password in an LDAP directory, denying authorization in case - the password is to old.
Authorize a user based on roles or an arbitrary LDAP filter expression.
- Authorize a user based on whether he owns a file or belongs to the group owning a file.
The module can perform an ordinary LDAP authentication using an LDAP bind call, but is incapable of verifying an SHA1 or crypt password hash from the directory, as mod_auth_ldap can.
The module also tries to do reduce LDAP connection overhead by caching a connection between requests (one per server record). This is most likely to improve performance in the case of certificate authentication, as for basic authentication a bind to the directory on a new connection is necessary with every request. Future development may add a cache to improve performance.
Version 0.8 added the ability to use the cache built into some client libraries, most notably OpenLDAP. However, it turned out that the cache for OpenLDAP 2.0.7 does not work, and only causes Apache to dump out the contents of BER buffers instead of authenticating users.
mod_authz_ldap uses some functions from libraries that are only available on Unix systems, it will most probably not work on a Win32 system. There are no plans to fix this problem.
Of course there are other modules that perform LDAP authentication. Not mentionning them here does not mean that they are insignificant, quite the contrary is true. But as far as I know, none of these alternatives does either certificate mapping or password aging.