Free http mobileagent vodafone 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.

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.

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).

media-box is a program to watch all kind of multimedia files using a computer.
It suports playing DVD video, VideoCD, various movie files, Audio CD, various music files and watching various still pictures.
Main goal of this project is to have a dedicated computer in your living room by replacing your Hi-Fi component (DVD-player, CD-player). media-box runs in a linux environment so the need for computer power is very low.
Prefered system is a computer with at least 466MHz Celeron with 128MB of ram. Disk space is minimal, it works on 1GB partition but it can sure fit on a partition of 150MB or even less.
As it considers the sound output it is considered to have a sound card with digital out capabilities, so you can easily connect your computer with a dedicated external Dolby Digital receiver, but this is optional.
Graphics card should have a TV-Out feature, so you can watch your media content on TV. For getting the remote control over the whole program, you should make a hardware receiver or you can even buy one. Just make sure it is lirc compatible.
Software used to make this hardware work:
- debian - linux distribution
- xine-lib - library to play media content
- ati.2 - ATI drivers for XFree86 4.2.1 - to get TVOut working
- alsa - SB Live! drivers to get digital out sound
- lirc - remote control software
Enhancements:
- created upgrade script so on pressing n in main window will start an upgrade
- fixed start.sh script to use the /media-box/XF86Config-4 file
- size of screen is now calculated from the width and height of the back.jpg picture (was fixed to 800x600) - beware tvout works only on 800x600.
- fixed background of movie so it is black now. Subtitles of new xine lib displayed background image.
- added new types of files to play (based on extension)
- audio
- aac
- mp4

HTTP::Browscap is a Perl module that can parse and search browscap.ini files.

SYNOPSIS

use HTTP::Browscap;

my $capable = browscap();

if( $capable->{wap} ) {
output_WAP();
}

if( $capable->{css} > 1 ) {
# Browser can handle CSS2
}

# OO interface
my $BC = HTTP::Browscap->new( browscap.ini );

$capable = $BC->match( $ENV{HTTP_USER_AGENT} );

ABSTRACT

Browscap.ini is a file, introduced with Microsofts IIS, that lists the User-Agent strings that different browsers send, and various capabilities of those browsers. This module parses browscap.ini and allows you to find the capability definitions for a given browser.

Starting with Microsofts IIS, a browscap.ini file was used to list the capabilities of various browsers. Using the User-Agent string that a browser sends in the HTTP request, the capabilities of a browser are retrieved. If an exact match of the User-Agent string isnt found, wild-card expantion is done. If all fails, a default browser definition is used.

There are limits the usefulness of browscap.ini. It only detects if a browser has a certain capability, but not if this capability has been deactivated or if its a buggy implementation. In particular, most CSS and JavaScript implementations will make you scream.

wgrab http file fetcher provides a small, fast, and cross platform wget alternative.
wgrab is an HTTP file fetcher similar to wget that is designed to be small, fast, and cross-platform compatible natively. The compiled wgrab is approximately 1/10th the size of wget, making it ideal for distributions like DSL and other miniature distributions.
Enhancements:
- fixed a spelling error in the --help output
- fixed the --timeout help being reported for --ignore-errors
- updated the installer to contain color coded responses if possible
- fixed "Network no reachable" error if no url was specified