Free rpc http outlook software for linux

The HTTP Time Protocl (HTP) system is a set of utilities to set and maintain the system clock from the HTTP/1.1 (RFC 2616) "Date:" header. HTP requires Libconfig.
The purpose of HTP is provide a simple to use system that can be used on any system that is connected to the internet and can access atleast one web page (either directly or through a proxy) to be able to maintain an accurate clock.
HTTP Time Protocol uses basic statistical analysis to arrive at the most accurate time possible given enough servers. The more servers HTP is configured to use the more accurate the clock can be.
Enhancements:
- Cleanup/simplification of the code.
- A more robust implementation of the "-p" (precision) switch.

Jabber::RPC::HTTPgate is an HTTP gateway for Jabber-RPC / XML-RPC.

SYNOPSIS

use Jabber::RPC::HTTPgate;

my $gw = new Jabber::RPC::HTTPgate(
server => myserver.org:5701,
identauth => jrpchttp.localhost:secret,
httpcomp => http,
);

$gw->start;

Jabber::RPC::HTTPgate is an experimental gateway that provides a conduit service between traditional (HTTP-transported) XML-RPC encoded requests/responses and Jabber-RPC (XML-RPC encoded requests/responses transported over Jabber).

The idea is that you can start a gateway, that connects as a component to the backbone of a Jabber server, and it proxies Jabber-RPC to HTTP-based XML-RPC endpoints, and vice versa. That means that your Jabber-RPC client can not only make XML-RPC encoded calls to a Jabber-RPC endpoint but also to a traditional HTTP-based XML-RPC endpoint. And it also means that your traditional HTTP-based XML-RPC client can make XML-RPC encoded calls to a Jabber-RPC endpoint.

Jabber -> HTTP

When you create and start up a gateway, it listens for Jabber-RPC calls, just like a normal Jabber-RPC responder. On receipt of such a call, the gateway creates an HTTP request and sends this request on to the HTTP-based XML-RPC endpoint. The response received back from this HTTP call is relayed back to the original Jabber-RPC requester.
While a Jabber-RPC endpoint address is a Jabber ID (JID), an traditional XML-RPC endpoint address is a URL. So all the Jabber-RPC client needs to do is specify the URL in the resource part of the gateways endpoint JID.

HTTP -> Jabber

As well as listening for Jabber-RPC calls, a gateway will also service incoming HTTP requests that can be made to the HTTP component that this gateway uses. The HTTP component (called simply http) can be downloaded from the normal Jabber software repository.

On receipt of an HTTP request (passed to it by the HTTP component), the gateway creates a Jabber-RPC request containing the XML-RPC encoded payload, and sends it on to the Jabber-RPC responder endpoint. This endpoint is identified (via a JID) by the path part of the URL used in the call by the traditional client.

HTTP Proxy Client is the small set of libraries and scripts, which provides transparent access to Internet via HTTP proxy for programs, which uses TCP/IP for communication.
The list of programs includes: telnet, ftp, licq, cvs, smth else? Project implements dynamic library, that can be preloaded before program run.
The library substitutes some system calls (connect(), gethostbyaddr(), gethostbyname()), with calls, which makes TCP/IP connection through HTTP proxy. This allows client programs behind HTTP proxy work with Internet without limitations.
At the moment tested on i386 Linux, i386/sparc Solaris.
Enhancements:
- While using dotted address, applications will attempt to connect regardless DNS lookup result.

lns.http is a simple framework for writing Common Lisp web applications. The project handles the incoming connections, parses HTTP headers and queries, and finally hands control over to your URL handler.

lns.http is a HTTP/1.1 compatible web server but tries to achieve compatibility with lesser (down to the informal HTTP/0.9) clients.

The lns.http web server uses lisp-network-server to take care of network handling.

This software is licensed unter the LGPL.

Monkey is a Web server written in C that works under Linux. This is an open source project based on the HTTP/1.1 protocol.
The objective is to develop a fast, efficient, small and easy to configure web server. If you wish to contribute to this project as a beta-tester, submitting suggestions and constructive criticisms, just contact me. Your input is welcome.
Main features:
- Get, Post & Head method
- CGI & PHP
- Multithreading
- Config files
- Mime types
- VirtualHost
- Directories navigation
- Users home
- Deny by URL & IP
- Resume

HTTP::MobileAgent::DoCoMo is a NTT DoCoMo implementation.

SYNOPSIS

use HTTP::MobileAgent;

local $ENV{HTTP_USER_AGENT} = "DoCoMo/1.0/P502i/c10";
my $agent = HTTP::MobileAgent->new;

printf "Name: %sn", $agent->name; # "DoCoMo"
printf "Ver: %sn", $agent->version; # 1.0
printf "HTML ver: %sn", $agent->html_version; # 2.0
printf "Model: %sn", $agent->model; # "P502i"
printf "Cache: %dkn", $agent->cache_size; # 10
print "FOMAn" if $agent->is_foma; # false
printf "Vendor: %sn", $agent->vendor; # P
printf "Series: %sn", $agent->series; # "502i"

# only available with
# e.g.) "DoCoMo/1.0/P503i/c10/serNMABH200331";
printf "Serial: %sn", $agent->serial_number; # "NMABH200331"

# e.g.) "DoCoMo/2.0 N2001(c10;ser0123456789abcde;icc01234567890123456789)";
printf "Serial: %sn", $agent->serial_number; # "0123456789abcde"
printf "Card ID: %sn", $agent->card_id; # "01234567890123456789"

# e.g.) "DoCoMo/1.0/P502i (Google CHTML Proxy/1.0)"
printf "Comment: %sn", $agent->comment; # "Google CHTML Proxy/1.0

# e.g.) "DoCoMo/1.0/D505i/c20/TB/W20H10"
printf "Status: %sn", $agent->status; # "TB"

# only available in eggy/M-stage
# e.g.) "DoCoMo/1.0/eggy/c300/s32/kPHS-K"
printf "Bandwidth: %dkbpsn", $agent->bandwidth; # 32

# e.g.) "DoCoMo/2.0 SO902i(c100;TB;W30H16)"
print "XHTML compiant!n" if $agent->xhtml_compliant; # true

HTTP::MobileAgent::DoCoMo is a subclass of HTTP::MobileAgent, which implements NTT docomo i-mode user agents.

HTTP::OAI::Repository is a documentation for building an OAI compliant repository using OAI-PERL.

Using the OAI-PERL library in a repository context requires the user to build the OAI responses to be sent to OAI harvesters.

SYNOPSIS

use HTTP::OAI::Harvester;
use HTTP::OAI::Metadata::OAI_DC;
use XML::SAX::Writer;
use XML::LibXML;

# (all of these options _must_ be supplied to comply with the OAI protocol)
# (protocolVersion and responseDate both have sensible defaults)
my $r = new HTTP::OAI::Identify(
baseURL=>http://yourhost/cgi/oai,
adminEmail=>youremail@yourhost,
repositoryName=>agoodname,
requestURL=>self_url()
);

# Include a description (an XML::LibXML Dom object)
$r->description(new HTTP::OAI::Metadata(dom=>$dom));

my $r = HTTP::OAI::GetRecord->new(
header=>HTTP::OAI::Header->new(
identifier=>oai:myrepo:10,
datestamp=>2004-10-01
),
metadata=>HTTP::OAI::Metadata::OAI_DC->new(
dc=>{title=>[Hello, World!],description=>[My Record]}
)
);
$r->about(HTTP::OAI::Metadata->new(dom=>$dom));

my $writer = XML::SAX::Writer->new();
$r->set_handler($writer);
$r->generate;