Free rfc 3261 software for linux

This Tcl script may be used to extract MIB, PIB and ASN.1 modules from an RFC document.

Unlike most extractors, this script is smart enough to recognize ASN.1-style comments prior to or within the module header, use of the "TagDefaults" part of the module header (not used by MIB modules), module headers that are broken across multiple lines, and macros.

SAP::Rfc is a Perl module that contains RFC Function calls against an SAP R/3 System.

SYNOPSIS

# WARNING - as of SAP::Rfc 1.40 USER and PASSWD are case sensitive ready for
# R3 7.x
use SAP::Rfc;
$rfc = new SAP::Rfc(
ASHOST => myhost,
USER => ME,
PASSWD => secret,
LANG => EN,
CLIENT => 200,
SYSNR => 00,
TRACE => 1 );

my $it = $rfc->discover("RFC_READ_TABLE");

$it->QUERY_TABLE(TRDIR);
$it->ROWCOUNT( 2000 );
$it->OPTIONS( ["NAME LIKE RS%"] );

# or pass a list of hash refs like so:
$it->OPTIONS( [ { TEXT => "NAME LIKE RS%" } ] );

$rfc->callrfc( $it );

print "NO. PROGS: ".$it->tab(DATA)->rowCount()." n";
print join("n",( $it->DATA ));

$rfc->close();

SAP::Rfc - is a Perl extension for performing RFC Function calls against an SAP R/3 System. Please refer to the README file found with this distribution. This Distribution also allows the creation of registered RFCs so that an SAP system can call arbitrary Perl code created in assigned callbacks.

The best way to describe this package is to give a brief over view, and then launch into several examples. The SAP::Rfc package works in concert with several other packages that also come with same distribution, these are SAP::Iface, SAP::Parm, SAP::Tab, and SAP::Struc. These come together to give you an object oriented programming interface to performing RFC function calls to SAP from a UNIX based platform with your favourite programming language - Perl. A SAP::Rfc object holds together one ( and only one ) connection to an SAP system at a time. The SAP::Rfc object can hold one or many SAP::Iface objects, each of which equate to the definition of an RFC Function in SAP ( trans SE37 ). Each SAP::Iface object holds one or many SAP::Parm, and/or SAP::Tab objects, corresponding to the RFC Interface definition in SAP ( SE37 ).

For all SAP::Tab objects, and for complex SAP::Parm objects, a SAP::Struc object can be defined. This equates to a structure definition in the data dictionary ( SE11 ). Because the manual definition of interfaces and structures is a boring and tiresome exercise, there are specific methods provided to automatically discover, and add the appropriate interface definitions for an RFC Function module to the SAP::Rfc object ( see methods discover, and structure of SAP::Rfc ).

Please note that USER and PASSWD are now case sensitive - this change has the potential to break backward compatibility.

R3.pm is a Perl object oriented client interface to SAP R/3 using RFCSDK.

SYNOPSIS

use R3;
$conn = new R3::conn (host=>$host, sysnr=>$sysnr, client=>$client,
user=>$usr, passwd=>$passwd);
$itab = new R3::itab ($conn, $table_name);
$func = new R3::func ($conn, $func_name);
...

R3.pm provides an object oriented interface to SAPs RFCSDK for connection to an R/3 system. R3::conn is the object interface to R/3 connections. R3::itab is the object interface to ABAP internal tables. R3::func is the object interface to ABAP RFC enabled functions.

babel-ircd is a small IRC server aimed for small communities. It supports a subset of RFC1459.
It extends the RFC by providing automatic encoding translation. The project only works in stand-alone on one server.
Exemple of lacks : modes (like operator)
new server command : /encoding
- /encoding iso-8859-1 set the encoding of the client to iso 8859-1. The server then convert all the message from and to this client to the right encoding. With this several clients can have different encoding and see their accents. All encoding provided by iconv are available
- /encoding list returns the list of supported encodings
- /encoding shows the current encoding
This software is under the GPLv2 License.
Enhancements:
- Tested with: xchat gaim ChatZilla Zircon KSirc LostIrc ircII BitchX tirc epic4 TinyIRC

URI::Escape is a Perl module to escape and unescape unsafe characters.

SYNOPSIS

use URI::Escape;
$safe = uri_escape("10% is enoughn");
$verysafe = uri_escape("foo", " -377");
$str = uri_unescape($safe);

This module provides functions to escape and unescape URI strings as defined by RFC 2396 (and updated by RFC 2732). A URI consists of a restricted set of characters, denoted as uric in RFC 2396. The restricted set of characters consists of digits, letters, and a few graphic symbols chosen from those common to most of the character encodings and input facilities available to Internet users:

"A" .. "Z", "a" .. "z", "0" .. "9",
";", "/", "?", ":", "@", "&", "=", "+", "$", ",", "[", "]", # reserved
"-", "_", ".", "!", "~", "*", "", "(", ")"

In addition, any byte (octet) can be represented in a URI by an escape sequence: a triplet consisting of the character "%" followed by two hexadecimal digits. A byte can also be represented directly by a character, using the US-ASCII character for that octet (iff the character is part of uric).

Some of the uric characters are reserved for use as delimiters or as part of certain URI components. These must be escaped if they are to be treated as ordinary data. Read RFC 2396 for further details.

PyGopherD provides a modern, multi-protocol hierarchical Gopher/HTTP server.

PyGopherD is a modern Gopher server. It can serve documents with Gopher+, standard Gopher (RFC 1436), and HTTP all on the same port.

It features a modular extension system, loadable scripts, and more.

It contains full support for UMN gopherd systems, including .Links, .names, .cap, searches, etc.

It also supports Bucktooth features such as gophermap files and executables, along with its own extra features.

Whats New in This Release:

This release adds virtual filesystem support, a VFS_ZIP module for using ZIP files to transparently hold part or all of your site, built-in WAP/WML support for serving your site to mobile phones, official support for Python 2.3, and bugfixes for stricter HTTP header conformance and minor HTML handling problems.

sip-redirect is a tiny SIP redirect server. sip-redirect supports IPv4 and IPv6, but the IPv6 support is optional.

The RFC 3261 was the base for this simple and very configurable implementation. There is neither TCP nor multicast support programmed in.