Free objective modula 2 1.00 reference implementation software for linux

Requirements:

• Python

Procinfo NG is a ground-up rewrite of the procinfo program. Procinfo NGs goal is to make the code more readable (and reusable) and to restore broken functionality of the original program.
The original program was written for Linux 1.0, and updated through 2.2. This version is for 2.6.
Enhancements:
- Updates were made to match what some Linux distributions have done to procinfo-18.
- Support for MSI and XEN interrupts were added.
- Some non-x86 architectures are handled.
- Assorted bugs and 80-character console nonsense were fixed.

Bloo is a free, public-domain, object-oriented implementation of full-featured blog software, based on the Phoo Phramework. Both Phoo and Bloo are PHP systems. This projects are both covered under the Gnu Public License.
Main features:
- Role-based security at the object level (in other words, security is pervasive)
- Those with posting privileges can create and edit posts
- Readers can comment on posts
- Posts can receive trackbacks
- Comment and trackback moderation, spam and troll destruction, etc.
- Administrators have full control over the look and feel of the blog, via the overlay editor. All visual element templates can be edited on the fly, with a non-destructive edit.
- Themes control the look and feel. Administrators can create themes on the fly, cascade themes from other themes, and select the default theme.
- Optional theme-selector for blog readers to pick their favorite theme
- Bloo-administered Blogroll ("Bloogroll")
- Configurable blogroll categories
- Multiple Spam Control Extension SnapOns
- Multiple users
- Multiple post categories per post.
- Post keyword searches
- Easy to use installation and upgrade programs
- Developers can create new Extension SnapOns to add functionality to the blog
- All input and output components of the system are XML-based and separate from the code
- New functionality can be added via Bloo Extension SnapOns
Enhancements:
- New features in this release include support for multiple post categories, IP blacklist and comments-flood protection, an enhanced theme selector, RSS fixes, among others.

Restlet is a framework that brings the simplicity and efficiency of the REST architectural style to Java developers.
Restlet project is composed of two parts, a neutral API and a reference implementation (Noelios Restlet Engine). It supports all REST concepts (resource, representation, data, connector, components, etc.) and is suitable for both client and server REST applications.
The server connectors provided are HTTP (via Mortbays Jetty or an adapter Servlet) and the client connectors are HTTP, JDBC, and SMTP (via JavaMail).
Mission
- Bring the simplicity and efficiency of the REST architectural style to Java developers
Restlet API
- Supports all REST concepts (resource, representation, data, connector, components, etc.)
- Suitable for both client and server Web applications
- Maplets support the concept of URIs as UI with advanced pattern matching features
- Chainlets filter calls to implement features such as logging and authentication
- Complete alternative to Servlet API with no external dependency (JAR < 60kb)
- Supports blocking and non-blocking NIO modes
Noelios Restlet Engine (NRE)
- Reference implementation of the Restlet API provided by Noelios Consulting (core JAR < 110kb)
- Server connector provided: HTTP (via Jetty connectors or Servlet connector)
- Client connectors provided: HTTP, JDBC, SMTP (via JavaMail)
- Supports logging (LogChainlet), authentication (GuardChainlet) and cool URIs rewriting (RedirectRestlet)
- Static files serving (DirectoryRestlet) with metadata association based on file extensions
- FreeMarker template representations as an alternative to JSP pages
- Automatic server-side content negotiation based on media type and language

Devel::Pointer is a Perl module that can fiddle around with pointers.

SYNOPSIS

use Devel::Pointer;
$a = address_of($b); # a = &b;
$b = deref($a); # b = *a;

$a = unsmash_sv(0+$scalar_ref);
@a = unsmash_av(0+$array_ref);
%a = unsmash_hv(0+$hash_ref);
&a = unsmash_cv(0+$code_ref);
# OK, you cant do that, but you get the idea

$c = deref(-1); # *(-1), and the resulting segfault.

The primary purpose of this is to turn a smashed reference address back into a value. Once a reference is treated as a numeric value, you cant dereference it normally; although with this module, you can.

Be careful, though, to avoid dereferencing things that dont want to be dereferenced.

Sunrise Data Dictionary is a library for hashtable storage of arbitrary data objects with built-in reference counting and guaranteed order iteration for the C programming language.
Sunrise Data Dictionary library can participate in external reference counting systems or use its own built-in reference counting. It comes with a variety of hash functions and allows the use of runtime supplied hash functions via callback mechanism. The source code is well documented.
The Sunrise Data Dictionary was specifically designed for use within the Afelio and Callweaver telephony servers, the implementation focuses on performance and scalability.
Enhancements:
- This is the initial release of the full API (all header files) and a developer snapshot of the implementation.

The "Open Device Monitoring and Tracking Protocol", otherwise known as OpenDMTP, is a protocol and framework that allows bi-directional data communications between servers and devices (clients) over the Internet and similar networks.
OpenDMTP is a highly configurable and extensible protocol for communicating with mobile devices.
OpenDMTP is particularly geared towards Location-based information (LBS) such as GPS, as well as temperature and other data collected in remote-monitoring devices. OpenDMTP is small, and is especially suited for micro-devices such as PDAs, mobile phones, and custom OEM devices.
We saw a need for a communications protocol that allowed high-latency, low-bandwidth (HL/LB) devices to transmit location data to monitoring-systems. Because these devices often have limited network connectivity, the protocol needed to be small and efficient. Example devices include mobile phones, PDAs, OEM micro-devices (alarm systems, temperature monitors, etc.), and more.
There are many mobile GPS tracking devices on the market today with their own closed proprietary protocols. Searching the web for open protocols revealed only a few available for transferring data (including GPS information) between devices. However these solutions are generally designed for non-mobile applications and/or lack some of the low-bandwidth, configurable, and extensible features that mobile applications require.
Main features:
- Small Footprint: Mobile devices typically have limited resources on which to run client code (ie. memory, processor speed). An open protocol designed with this in mind should be optimized to allow efficient implementation and should easily support devices such as PDAs, mobile phones, GPS monitoring devices, and other OEM micro-devices.
- Network Efficient: Mobile devices typically have limited network connectivity, and in some cases data communication can be quite expensive (e.g. satellite). Because of this the protocol needs to be efficient in its dialog between the client and server. The communication needs to be optimized such that the necessary information can be conveyed with a minimum number of bytes in the least amount of time.
- Bi-directional: Some devices can support two-way communication (ie. GPRS, or other socket based connections), while others may only support one-way communication (ie. some satellite communication systems). With this in mind, a protocol should be designed to support both duplex (two-way) and simplex (one-way) communication.
- Transport Media: Differrent mobile applications will have their own unique way of communicating data back to the server. Some may use GPRS, or socket based communication, others may use satellite communication, while still others may use other forms of wireless communication, such as BlueTooth. The design of the protocol should be able to encompass all such transport media types, regardless of the type of transport in use.
- Flexible Data Encoding: Most types of transport media allow for the transmission of binary encoded data. However, there may be some forms of media for which an ASCII encoded data packet is much better suited. A protocol designed with this in mind should be able to support both types of data encoding.
- Configurable Messages: Due to the broad range of data types used in mobile applications, the protocol should be flexible enough to define standard messages, yet still allow custom messages within the framework.
- Extensible: Not every mobile application is the same. Some require special handling and may have various types of inputs and outputs. A protocol designed for mobile applications should insure that the framework can be easily extended to incapsulate the specific needs of the device.
- Industry Compatibility: Having an open protocol insures better compatibility between different client devices and service providers.
- Reference Implementation: Having a reference implementation that showcases the major features of the protocol provides an easy starting point on which developers can add their own features and platform specific implementation without having to worry about how data gets from the client to the server.
OpenDMTP was specifically designed to suit all these needs, especially "Small Footprint" and "Network Efficiency". The typical data plan for GPRS communication, for instance, is usually 1Mb per month. OpenDMTP was designed to optimize packet encoding to allow the collection of GPS information packets once every 3 minutes, 24 hours a day, 30 days a month, and still stay under the 1Mb data plan limit.
While XML is very extensible, it fails the "Small Footprint" and "Network Efficiency" requirements. Thus, it was discounted as a viable protocol solution. Many mobile devices do not have the resources necessary to be able to provide full XML parsing functionality. And an XML packet may need to be several hundred bytes in length just to send a few bytes of actual data. This alone would make the solution cost prohibitive for high-cost transport media such as satellite.
OpenDMTP also includes a full-featured commercial quality reference implementation to jump-start development.
Enhancements:
- NEW: Minor optimizations made to message logging.
- FIX: Log file now properly displays account/device on client connection.

ISC DHCP provides a freely redistributable reference implementation of all aspects of DHCP, through a suite of DHCP tools:
- A DHCP server
- A DHCP client
- A DHCP relay agent
These tools all use a modular API which is designed to be sufficiently general that it can easily be made to work on POSIX-compliant operating systems and also non-POSIX systems like Windows NT and MacOS.
The DHCP server, client and relay agent are provided both as reference implementations of the protocol and as working, fully-featured sample implementations.
Both the client and the server provide functionality that, while not strictly required by the protocol, is very useful in practice. DHCP server also makes allowances for non-compliant clients which one might still like to support.