Free user agent software for linux

App::UserAgent - the browser this session is connected to.

SYNOPSIS

# ... official way to get a UserAgent object ...
use App;
$context = App->context();
$user_agent = $context->user_agent(); # get the user_agent

if ($user_agent->supports("html.input.style")) {
# do something
}

A UserAgent class models the browser connected to this session. It is used to determine what capabilities are supported by the user agent.

Constructor Methods:

new()

The App::UserAgent->new() method is rarely called directly. That is because a $user_agent should always be instantiated by getting it from the $context [ $context->user_agent() ].

* Signature: $user_agent = App::UserAgent->new($context);
* Signature: $user_agent = App::UserAgent->new();
* Param: $context App::Context
* Return: $user_agent App::UserAgent
* Throws:
* Since: 0.01

Sample Usage:

[Common Use]
$context = App->context();
$user_agent = $context->user_agent();

[Internal Use Only]
$user_agent = App::UserAgent->new();

Mobile::UserAgent is a mobile user agent string parsing class.

SYNOPSIS

### Print the information parsed from a user-agent string:
use Mobile::UserAgent;
my $useragent = Nokia6600/1.0 (4.09.1) SymbianOS/7.0s Series60/2.0 Profile/MIDP-2.0 Configuration/CLDC-1.0;
my $uaobj = new Mobile::UserAgent($useragent);
if ($uaobj->success()) {
print Vendor: . $uaobj->vendor() . "n";
print Model: . $uaobj->model() . "n";
print Version: . $uaobj->version() . "n";
print Series60: . $uaobj->isSeries60() . "n";
print Imode?: . $uaobj->isImode() . "n";
print Mozilla?: . $uaobj->isMozilla() . "n";
print Standard?: . $uaobj->isStandard() . "n";
print Rubbish?: . $uaobj->isRubbish() . "n";
}
else {
print "Not a mobile user-agent: $useragentn";
}


### Determine if the client is a mobile device.
use Mobile::UserAgent ();
use CGI ();

# Check 1: (check if it sends a user-agent profile URL in its headers)
foreach my $name (X_WAP_PROFILE,PROFILE,13_PROFILE,56_PROFILE) {
if (exists($ENV{"HTTP_$name"})) {
print "Client has a user-agent profile header, so its probably a mobile device.n";
last;
}
}

# Check 2: (check if it supports WML):
my $q = new CGI();
if ($q->Accept(text/vnd.wap.wml) == 1) {
print "Client supports WML so its probably a mobile device.n";
}

# Check 3: (check if this class can parse it)
my $uaobj = new Mobile::UserAgent();
if ($uaobj->success()) {
print "Clients user-agent could be parsed, so its a mobile device.n";
}

Parses a mobile user agent string into its basic constituent parts, the most important being vendor and model.

One reason for doing this would be to use this information to lookup vendor-model specific device characteristics in a database. You can use also use user agent profiles to do this (for which Ive developed other classes), but not all mobile phones have these, especially the older types. Another reason would be to detect if the visiting client is a mobile handset.

Only real mobile user-agent strings can be parsed succesfully by this class. Most WAP emulators are not supported because they usually dont use the same user-agent strings as the devices they emulate.

Agent is the Transportable Agent Perl module.

SYNOPSIS

use Agent;

my $a = new Agent( Name => path_to_agent.pa, %args );

$a->run();

Agent Perl is meant to be a multi-platform interface for writing and using transportable perl agents.

A Perl Agent

Is any chunk of Perl code that can accomplish some user-defined objective by communicating with other agents, and manipulating any data it obtains.
A Perl Agent consists of a knowledge base (variables), a reasoning procedure (code), and access to one or more languages coupled with methods of communication. These languages remain largely undefined, or rather, user-defined; support for KQML/KIF is under development.

Developing An Agent

Note that the developer must devise the reasoning procedure and knowledge base described above. Agent Perl does not place any restrictions on what you may do; it only tries to make the doing part easier.

An agent is written as an inheriting sub-class of Agent. Each agents class should be stored in a .pa file (perl agent), and must contain an agent_main() method. All agents are objects. See the examples for more details, and learn how Agent.pm works so you wont step on its toes!

xmms-agent hides XMMS into system tray and allows controlling it from tray icons popup menu.
This application is written in some minutes for my own need, so dont expect it would some case of great stuff.
Id tried to find similar thing for XMMS, but I couldnt, so once Ive just decided to make my own wrapper.
Ill be glad if youll find this program useful.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes a while. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Type `make install to install the programs and any data files and documentation.
4. You can remove the program binaries and object files from the source code directory by typing `make clean.
Enhancements:
- Pretty little improvement: now xmms pops up on active desktop.

Junk Mail Buffering Agent is a tool for preventing delivery of email until the sender has confirmed their address.

Junk Mail Buffering Agent can be used in conjunction with a spam filter to prevent delivery of spammy-looking email unless the sender is confirmed as valid.

jmba is designed to be used in conjunction with a spam filter such as QSF and the mail processor procmail. When the spam filter says it thinks an email is spam, it can be passed to jmba.

jmba will queue it and send an email to the sender containing a key; if the sender replies, the original email is "unfrozen" from the queue and delivered.

rPath Appliance Agent project is an extensible application framework for the administration of appliance devices through a web-based user interface.
The framework is comprised of individual component plugins which offer specialized functionality, such as a message log interface, user account preferences, system updates, and entitlement management capabilities.
You can also develop and add plugins to the rAA framework, extending capabilities and functionality for your specific requirements.
To set up your environment for developing rAA, untar the devel.tar.bz2 tarball in the docs directory into your development directory. It should contain the following files:
- README.devel:
this file.
- dev.cfg:
configuration for the development environment.
- raa:
symbolic link to the rAA installation, usually
/usr/lib/python2.4/site-packages/raa.
- raa-service:
used by the startup script for the rAA service daemon.
- raa_service_dev.conf:
configuration file for the rAA service daemon. This contains a pluginDirs
configuration option. Change or append to its value to add additional
directories in which you are developing plugins.
- raa-web:
startup script for the rAA web layer.
- start-raa-service.sh:
startup script for the rAA service daemon.
Enhancements:
- Enhancements to the backup plugin, and a new plugin has been added to allow users to upload new SSL certificates for rAAs Web servers HTTPS connections.