Free api 2.0 software for linux

Monitoring API project is a multi-user programming interface designed to simplify the development of network monitoring software and allows users to express their monitoring needs in a device-independent way.
The main abstraction provided by MAPI is the network flow. Although flows have been used before in network monitoring systems, MAPI gives flows a first-class status. Applications that uses MAPI can specify what flows or flow statistics they are interested in by applying functions to flows.
A MAPI function can be a BPF filter, string search, packet counter or more advanced like a NetFlow generator. These function will automatically run in hardware if there is support for it on the hardware being used.
MAPI currently supports the following hardware:
- Normal NICs through libpcap
- DAG cards without co-processor
- SCAMPI adapter
Enhancements:
- This release includes support for distributed monitoring, several new MAPI functions, demo applications, and a lot of bugfixes.

PDL::API is a Perl module for making piddles from Perl and C/XS code.

A simple cookbook how to create piddles manually. It covers both the Perl and the C/XS level. Additionally, it describes the PDL core routines that can be accessed from other modules. These routines basically define the PDL API. If you need to access piddles from C/XS you probably need to know about these functions.

SYNOPSIS

use PDL;
sub mkmypiddle {
...
}

APR::Brigade is a Perl API for manipulating APR Bucket Brigades.

Synopsis

use APR::Brigade ();

$bb = APR::Brigade->new($r->pool, $c->bucket_alloc);
$ba = $bb->bucket_alloc();
$pool = $bb->pool;

$bb->insert_head($b);
$bb->insert_tail($b);

$b_first = $bb->first;
$b_last = $bb->last;

$b_prev = $bb->prev($b_last);
$b_next = $bb->next($b);

$bb2 = APR::Brigade->new($r->pool, $c->bucket_alloc);
$bb1->concat($bb2);

$len = $bb->flatten($data);
$len = $bb2->flatten($data, $wanted);

$len = $bb->length;
$bb3 = $bb->split($b_last);

last if $bb->is_empty();
$bb->cleanup();

The DLini library provides functions for reading and writing Windows style .ini files.
It mimics the Windows API for .ini file handling exactly, so it can be used to port Windows applications that use .ini files to other platforms.
Have you ever needed to port a Windows program to Linux or UNIX? Maybe its a legacy program and uses .ini files to read its settings.
This package provides all the necessary functions to read the .ini file, in just the same way as you would expect to read it under Windows using GetPrivateProfile style functions.
Enhancements:
- New functions completed: GetPrivateProfileStruct, GetPrivateProfileSection, and GetPrivateProfileSectionNames.
- Some optional debug output and an off-by-one error have been corrected.
- Autoconf/Automake scripts have been added.

Jetspeed provides a JSR-168 compliant enterprise portal.
etspeed-2 is a full implementation of the Java Portlet API. It is fully compliant with the Portlet Specification 1.0 (JSR-168). It has passed the TCK (Test Compatibility Kit) suite and is fully CERTIFIED to the Java Portlet Standard.
Notable features include security components backed by LDAP and database implementations, and some robust administration interfaces. Custom portals can be built and deployed using the Jetspeed plugin for Maven.
Developers can use the Jetspeed PSML language to assemble portlets, and the Apache Portals Bridges project to bridge portals with existing technologies including Struts, JSF, PHP, and Perl.
For GUI designers, Jetspeed comes with several built-in templates used to decorate portals and portlets.
Main features:
- Fully compliant with Java Portlet API Standard 1.0 (JSR 168)
- Passed JSR-168 TCK Compatibility Test Suite
- J2EE Security based on JAAS Standard, JAAS DB Portal Security Policy
- LDAP Support for User Authentication
- Spring-based Components and Scalable Architecture
- Configurable Pipeline Request Processor
- Auto Deployment of Portlet Applications
- Jetspeed Component Java API
- Jetspeed AJAX XML API
- Declarative Security Constraints and JAAS Database Security Policy
- Runtime Portlet API Standard Role-based Security
- Portal Content Management and Navigations: Pages, Menus, Folders, Links
- Multithreaded Aggregation Engine
- PSML Folder CMS Navigations, Menus, Links
- Jetspeed SSO (Single Sign-on)
- Rules-based Profiler for page and resource location
- Integrates with most popular databases including Derby, MySQL, MS SQL, Postgres, Oracle, DB2, Hypersonic
- Client independent capability engine (html, xhtml, wml,vml)
- Internationalization: Localized Portal Resources in 12 Languages
- Statistics Logging Engine
- Portlet Registry
- Full Text Search of Portlet Resources with Lucene
- User Registration
- Forgotten Password
- Rich Login and Password Configuration Management

libmtp is an implementation of Microsofts Media Transfer Protocol (MTP) in the form of a library suitable primarily for POSIX compliant operating systems.
libmtp is based on (forked from) the great libptp2 library by Mariusz Woloszyn.
Installation:
Problems with compilation under FC4: GCC4 related problem.
Run this:
CC=gcc32
export CC
./configure
make
Enhancements:
- It uses extended commands to retrieve and cache large metadata sets quickly.
- Is features VERY many new device ID:s and bug flags making it ever more interoperable.
- It fully supports 64bit filesizes. (We hope.).
- It produced udev rules for the new kernels.
- It produces a very bleeding edge HAL style .fdi file.
- Many, many other bug fixes. Notice that the album API in the libmtp.h file has changed somewhat, it should be quite easy to upgrade the existing code. However the album API still needs some overhaul. The library version is bumped to libmtp.so.6 as a consequence of the changes which affects distribution packaging and makes it necessary to recompile applications linking to libmtp.

Wikipedia API is a simple API to embed Wikipedia content dynamically on a Web site.

Wikipedia is an online encyclopedia in which the user community is encouraged to submit information for its entries. Wikipedia is unique in that it is free to the public, the content is fairly well moderated, and its content is licensed under the GFDL (GNU Free Documentation License); therefore, all of its text can be copied, modified, and used any way you see fit.

The only stipulation to using its text, is that the names of the original authors must remain intact. KillerTux.com is currently embedding some of the relevant entries in its own site and has decided to make the API open for public use. It is a simple implementation and should be easy to use. If you are a webmaster and would like to use KillerTux.coms Wikipedia API, this is the place to learn how to do it.

What is an API

An API is an application programming interface with which external applications can communicate with. The syntax and usage of the API dictates the type of data, format, and other specifics of the information to be exchanged. In this case, the API is a simple call to KillerTux.coms web server via the HTTP protocol.

Wikipedia API usage

The URL for the API is "http://scrapers.killertux.com/wikipedia-api.php". It uses the get request method and only has 3 parameters. These parameters are as follows:

wikititle=
wikiformat=[html | text]
wikiimages=[yes | no ]

The wikititle value is the name of the Wikipedia entry you are looking for, in Wikipedias variable entry. This can be found by going to Wikipedia.org and finding an entry. The name is the last part of the URL. For instance, the Wikipedia entry for "Computer Program" is "http://en.wikipedia.org/wiki/Computer_Program". Notice the space is an underscore in the URL. Defining the wikititle value for this API would look like this: wikititle=Computer_Program. This value must be specified. A sample API call would be "http://scrapers.killertux.com/wikipedia-api.php?wikititle=Computer_Program". The wikiformat value currently has two possible values: html and text. html is the default if no value is specified. If you use HTML format, it is recommended that a style sheet be used, although it may not be necessary.

A sample CSS is provided here. The text format option strips all HTML code from the document and returns plain text formatted at 80 characters per column. A sample API call would be "http://scrapers.killertux.com/wikipedia-api.php?wikititle=Computer_Program&wikiformat=html". The wikiimages value is only valid for HTML format; images for the text format are disabled. Image source locations are preserved and images are loaded from Wikipedia, not KillerTux.com. If wikiimages=no is selected, all images and captions will be striped from the document, while other HTML code should remain intact such as links to other articles. A sample API call would be "http://scrapers.killertux.com/wikipedia-api.php?wikititle=Computer_Program&wikiimages=no".

libmtag is a library for music tagging.
libmtags objective is to create the most simple yet useful tagging library for music.
It uses taglib as a backend, but provides a more generic API. In the future it might be possible to remove the dependency.
The programming language used is C, but bindings for Ruby and Python are provided.
As taglib, it supports: ID3v1, ID3v2 for MP3 files, Ogg Vorbis and FLAC files.
Enhancements:
- A new CLI application.
- A new get_type method (MP3, Vorbis, FLAC, etc.)