Free rfc 2833 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.

Riece is an IRC client for Emacs. Riece supports multiple server profiles, custom window layout, and other nice features.
Riece can be dynamically extended by add-on (plugin) modules. By default, 30 add-ons are available.
Main features:
- Several IRC servers may be used at the same time.
- Riece can be dynamically extended by add-on modules.
- Installation is easy. Riece doesnt depend on other elisp packages.
- Setup is easy. Automatically save/restore the configuration.
- Riece uses separate windows to display users, channels, and dialogues. Users can select the window layout.
- Step by step instruction is included.
- Mostly compliant with RFC 2812.
Enhancements:
- This release has a new add-on to enables secure conversation using GnuPG.

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.

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.

Ruby/DICT is an RFC 2229 compliant client-side library implementation of the DICT protocol, written in the Ruby programming language. Ruby/DICT library can be used to write clients that access dictionary definitions from a set of natural language dictionary databases. In the words of the RFC:

The DICT protocol is designed to provide access to multiple databases. Word definitions can be requested, the word index can be searched (using an easily extended set of algorithms), information about the server can be provided (e.g., which index search strategies are supported, or which databases are available), and information about a database can be provided (e.g., copyright, citation, or distribution information). Further, the DICT protocol has hooks that can be used to restrict access to some or all of the databases.

The archive also includes rdict, a dictionary client built on top of the Ruby/DICT library.

Here are some examples of its usage:

$ rdict -D

This will provide you with a list of databases you can query.

$ rdict -S

This will provide you with a list of strategies you can employ to match words.

$ rdict -m -s prefix foo

This shows you a list of all words that begin with foo in all of the databases.

$ rdict -m -s re ^(cu|ke)rb$

This shows you all the definitions relating to both curb and kerb from all the databases. The re strategy allows regular expression matching.

$ rdict -m -s suffix fix

This shows a list of all words that end in fix in all of the databases.

libircclient is a small but powerful library, which implements client-server IRC protocol. libircclient is designed to be small, fast, portable and compatible to RFC standards, and most IRC clients.
Main features:
- Full multi-threading support.
- Single threads handles all the IRC processing.
- Support for single-threaded applications, and socket-based applications, which use select()
- Synchronous and asynchronous interfaces.
- CTCP support with optional build-in reply code.
- Flexible DCC support, including both DCC chat, and DCC file transfer.
- Can both initiate and react to initiated DCC.
- Can accept or decline DCC sessions asynchronously.
- Plain C interface and implementation (possible to use from C++ code, obviously)
- Compatible with RFC 1459 and most IRC clients.
- Free, licensed under LGPL license.
- Good documentation and examples available.
Installation:
./configure
make
make install
Enhancements:
- IRC color manpulation functions now exported too.

OpenCAP is a server for Internet calendaring by following the specifications of the IETF (RFC CAP 4324).

Cap4j is the RFC 4234 CAP implementation. OpenCap project is the implementation of Cap4j calendar store.

Why another calendaring project ?

Ideally, Internet Calendaring should allow every Internet user to schedule meeting with each-other like they send mails. Unfortunately, Internet Calendaring suffers from a lack of interoperability. Thats why its so important to follow such standards.