Free http mobileagent jphone 0.26 software for linux

HTTP::MobileAgent::JPhone Perl module is a J-Phone implementation.

SYNOPSIS

use HTTP::MobileAgent;

local $ENV{HTTP_USER_AGENT} = "J-PHONE/2.0/J-DN02";
my $agent = HTTP::MobileAgent->new;

printf "Name: %sn", $agent->name; # "J-PHONE"
printf "Version: %sn", $agent->version; # 2.0
printf "Model: %sn", $agent->model; # "J-DN02"
print "Packet is compliant.n" if $agent->packet_compliant; # false

# only availabe in Java compliant
# e.g.) "J-PHONE/4.0/J-SH51/SNXXXXXXXXX SH/0001a Profile/MIDP-1.0 Configuration/CLDC-1.0 Ext-Profile/JSCL-1.1.0"
printf "Serial: %sn", $agent->serial_number; # XXXXXXXXXX
printf "Vendor: %sn", $agent->vendor; # SH
printf "Vender Version: %sn", $agent->vendor_version; # "0001a"

my $info = $self->java_info; # hash reference
print map { "$_: $info->{$_}n" } keys %$info;

HTTP::MobileAgent::JPhone is a subclass of HTTP::MobileAgent::Vodafone.

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.

HAVP (HTTP Antivirus Proxy) is a proxy with a ClamAV anti-virus scanner. HTTP Anti Virus Proxy aims are continuous, non-blocking downloads and smooth scanning of dynamic and password protected HTTP traffic.
Havp antivirus proxy has a parent and transparent proxy mode. It can be used with squid or standalone.
Main features:
- HTTP Antivirus proxy
- Scans complete incomming traffic
- Nonblocking downloads
- Smooth scanning of dynamic and password protected traffic
- Can used with squid or other proxy
- Parent proxy support
- Transparent proxy support
- Logfile
- Process change to defined user and group
- Daemon
- Use Clamav (GPL antivirus)
- Operating System: Linux
- Written in C++
- Released under GPL
Enhancements:
- Experimental support was added for chunked Transfer-Encoding, which fixes some broken sites.
- The IGNOREVIRUS configuration directive was added for whitelisting virus names.
- The CLAMBLOCKBROKEN configuration directive was added.
- Detection with AVG was improved.
- HAVP is killed if database reloading fails for Library Scanner.
- The URL is logged when a crashed scanner process is detected.
- The build system updated, adding the --prefix, --sbindir, --sysconfdir, and --localstatedir options.

Bigtop is a web application data language processor.

SYNOPSIS

See Bigtop::Docs::TentTut or Bigtop::Docs::Tutorial for how to create a Bigtop file. Bigtop::Docs::TOC is a guide to all of the documentation modules.
The real synopsis:

vi your_app.bigtop (or use tentmaker see Bigtop::Docs::TentTut)
bigtop --create your_app.bigtop all

Modify your bigtop file and try again:

bigtop docs/your_app.bigtop all

Bigtop is a language for describing the data of a web application. Usually this data will be stored in a relational database. Once you have a description of your data, you can generate a web application from it. This includes all the pieces you need like: the sql statements ready for feeding to your database command line tool, the httpd.conf you need to Include in the httpd.conf on your system, the modules that will handle the web requests, the models that make the database tables look like classes, etc.

If you need to alter the data model in the future, you can change your original description to match the new reality, then regenerate the application without fear of losing hand written code (though you may have to modify some of it to reflect the new reality).

FUNCTIONS

This module is really a place holder, but it does provide some developer routines (which are not exported):

write_file
use Bigtop;
Bigtop::write_file( $file_name, $file_content, $no_overwrite )

This attempts to write $file_content to $file_name and dies on failures of open or close. Further, if you pass a true no_overwrite flag, it will check to see if the file exists and refuse to overwrite it. In that case, the user gets a warning that the file has been skipped because it already exists. If you dont want the user to see the warning, turn off the Bigtop warning. To avoid fatal errors on write failures, wrap in an eval. Putting these together, we come to my typcial usage:

eval {
no warnings qw( Bigtop );
Bigtop::write_file( $some_output_file, $content, no_overwrite );
}
warn $@ if $@;
make_module_path

(Note that make_module_path uses File::Spec, so even though Unix directory syntax is shown below, the function should work in other places.)

use Bigtop;
Bigtop::make_module_path( $build_dir, $module_name );

This attempts to make all the directories from $build_dir to the home of the module. It assumes that lib comes immediately after $build_dir.

For example, a call like:

Bigtop::make_module_path(
/home/username/App-Name, App::Name::Subname
);
Attempts to make these directories:
/home/username/App-Name/lib
/home/username/App-Name/lib/App
/home/username/App-Name/lib/App/Name
/home/username/App-Name/lib/App/Name/Subname

It doesnt report failures. Making directories can fail because the directories already exist (in which case you probably dont care) or because they could not be written (in which case youll notice soon enough, when you try to write to them).

HTTP::Handle is a HTTP Class designed for streaming.

SYNOPSIS

use HTTP::Handle;

my $http = HTTP::Handle->new( uri => "http://www.google.com/" );
$http->connect();

my $fd = $http->fd();

while () {
print "--> $_";
}

The HTTP::Handle module allows you to make HTTP requests and handle the data yourself. The general ideas is that you use this module to make a HTTP request and handle non-header data yourself. I needed such a feature for my mp3 player to listen to icecast streams.

HTTP::Handle->new()

Create a new HTTP::Handle object thingy.

Arguments possible:

url => "http://www.google.com/"

Sets the initial URL to connect to.

follow_redirects => [ 0 | 1 ]

Automatically follow HTTP redirects. This defaults to true (1). Set to 0 to disable this.

http_request => HASHREF

Any thing put in here will be sent as "key: value" in the http request string.

$http->connect()

Connect, send the http request, and process the response headers.

This function returns -1 on failure, undef otherwise. The reason for failure will be printed to STDERR.

$http->fd()

Get the file descriptor (socket) were using to connect.

$http->url( [ url_string ])

Get or set the URL. If a url string is passed, you will change the url that is requested. If no parameter is passed, a URI object will be returned containing the

$http->follow_redirects( [ 0 | 1 ] )

If a value is passed then you will set whether or not we will automatically follow HTTP 302 Redirects. If no value is passed, then we will return whatever the current option is.

Defaults to 1 (will follow redirects).

$http->http_request_string()

Returns a string containing the HTTP request and headers, this is used when

$http->connect() is called.

HTTP::GetImages is a spider to recover and store images from web pages.

SYNOPSIS

use HTTP::GetImages;

$_ = new HTTP::GetImages (
dir => .,
todo => [http://www.google.com/,],
dont => [http://www.somewhere/ignorethis.html,http://and.this.html],
chat => 1,
);

$_->print_imgs;
$_->print_done;
$_->print_failed;
$_->print_ignored;

my $hash = $_->imgs_as_hash;
foreach (keys %{$hash}){
warn "$_ = ",$hash->{$_},"n";
}

exit;

This module allow syou to automate the searching, recovery and local storage of images from the web, including those linked by anchor (A), mage (IMG) and image map (AREA) elements.

Supply a URI or list of URIs to process, and HTTP::GetImages will recurse over every link it finds, searching for images.

By supplying a list of URIs, you can restrict the search to certain webservers and directories, or exclude it from certain webservers and directories.

You can also decide to reject images that are too small or too large.

Plasma EBG project is an Empire Building Game for Linux/Windows/Solaris/BSD.
Plasma EBG is an empire building game with an isometric view.
It runs in multiple resolutions with graphics being displayed better for higher resolutions; hence, lower resolutions do not suffer from being too large, etc. In the future several viewing engines will be available, such as EBG-opengl and EBG-2d.
There is a separate module called EBG-dev which features the latest AI-development, as well as a separate server module.
Enhancements:
- Plasma has had server problems in the past 2-2.5months. Hence this release is not that impressive - but it is long overdue.
- Many libraries have been updated/fixed... such as libpng (1.2.1), allegro (4.0.1).
- The new plasma server will be installed after easter some time - and soon after most planned features will be completed.

HTTP extension for PHP allows building absolute URIs, RFC-compliant HTTP redirects, RFC-compliant HTTP date handling, parsing of HTTP headers and messages, caching by "Last-Modified" and/or ETag (with an on the fly option for ETag generation from buffered output), sending data/files/streams with (multiple) ranges, negotiating user-preferred language/charset, and convenient request functionality built upon libcurl.
PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, and HttpMessage.
Main features:
- Building absolute URIs
- RFC compliant HTTP redirects
- RFC compliant HTTP date handling
- Parsing of HTTP headers and messages
- Caching by "Last-Modified" and/or ETag (with on the fly option for ETag generation from buffered output)
- Sending data/files/streams with (multiple) ranges support
- Negotiating user preferred language/charset
- Convenient request functionality built upon libcurl
- PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, HttpMessage.
Enhancements:
- This release fixes bug #11359: HttpMessage::toMessageTypeObject() does not populate POST fields.