Ports Search

The Hoard memory allocator is a fast, scalable, and memory-efficient memory allocator for shared-memory multiprocessors. Multithreaded programs that perform dynamic memory allocation do not scale because the heap is a bottleneck. When multiple threads simultaneously allocate or deallocate memory from the heap, they will be serialized while waiting for the heap lock. Programs making intensive use of the heap actually slow down as the number of processors increases. (Note: If you make a lot of use of the STL, you may not know it, but you are making a lot of use of the heap.) Hoard is a fast allocator that solves this problem. In addition, it has very reasonable bounds on memory consumption.

The module Data::Flow provides its services via objects. The objects may be obtained by the usual $request = new Data::Flow $recipes; paradigm. The argument $recipes is a hash reference, which provides the rules for request processing. The objects support two methods, set() and get(). The first one is used to provide input data for processing, the second one to obtain the output. The unit of requested information is a field. The method set() takes a pair field => value, the method get() takes one argument: the field. Every object is created without any fields filled, but it knows how to construct fields basing on other fields or some global into. This knowledge is provided in the argument $recipe of the new() function. This is a reference to a hash, keyed by fields. The values of this hash are hash references themselves, which describe how to acquire the field which is the corresponding key of the initial hash.

File::ShareDir::PAR provides the same functionality as File::ShareDir but tries hard to be compatible with PAR packaged applications. The problem is, that the concept of having a distribution or module specific share directory becomes a little hazy when you're loading everything from a single file. PAR uses an @INC hook to intercept any attempt to load a module. File::ShareDir uses the directory structure that is typically found in the directories that are listed in @INC for storing the shared data. In a PAR enviroment, this is not necessarily possible. WARNING: This module contains highly experimental code. If you want to load modules from .par files using PAR and then access their shared directory using File::ShareDir, you probably have no choice but to use it.

INTRODUCTION --- WHAT IS NOWEB, ANYWAY? noweb is a literate-programming tool like FunnelWEB or nuweb, only simpler. A noweb file contains program source code interleaved with documentation. When noweb is invoked, it writes the program source code to the output files mentioned in the noweb file, and it writes a TeX file for typeset documentation. noweb is designed to meet the needs of literate programmers while remaining as simple as possible. Its primary advantages are simplicity, extensibility, and language-independence. noweb works ``out of the box'' with any programming language, and supports TeX, latex, and HTML (Mosaic) back ends. A back end to support full hypertext or indexing takes about 250 lines; a simpler one can be written in 40 lines of awk. The primary sacrifice relative to WEB is that code is not prettyprinted. If you're brand new to literate programming, check out the FAQ for the USENET newsgroup comp.programming.literate. There are also some resources available through the noweb home page:

DHIS Daemon release 5.1 ============================== The server is now modular through the introduction of a services sub-system. DNS updates are no longer part of the main code but are now implemented as a module. The main dhisd process listens to DHIS clients and after authentication marks these with their dynamic IP address. The request is passed to a sub-process through a pipe which implements the services for which the client is subscribed to. Clients may be subscribed to one or more services individually. The sub-engine interface does a basic read from stdin and process. Examples of things DHIS could update: Dns, Firewalls, tunnel servers, relay access lists, etc ... For more information on the services of DHIS, you should look at the official DHIS site: http://www.dhis.org/dhis/services/

Dnsmasq is a lightweight, easy to configure DNS forwarder and DHCP server. It is designed to provide DNS and, optionally, DHCP, to a small network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated addresses to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP/TFTP/PXE for network booting of diskless machines. Dnsmasq is targeted at home networks using NAT and connected to the internet via a modem, cable-modem or ADSL connection but would be a good choice for any smallish network (up to 1000 clients is known to work) where low resource use and ease of configuration are important. -- Simon Kelley

Dnsmasq is a lightweight, easy to configure DNS forwarder and DHCP server. It is designed to provide DNS and, optionally, DHCP, to a small network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated addresses to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP/TFTP/PXE for network booting of diskless machines. Dnsmasq is targeted at home networks using NAT and connected to the internet via a modem, cable-modem or ADSL connection but would be a good choice for any smallish network (up to 1000 clients is known to work) where low resource use and ease of configuration are important. -- Simon Kelley

fpdns - Fingerprinting DNS servers A nameserver basically responds to a query. Interoperability is an obvious requirement here. The standard protocol behaviour of different DNS implementations is expected to be the same. Requirements for protocol behaviour of DNS implementations is widely documented in the case of 'common' dns messages. The DNS protocol is over 20 years old and since its inception, there have been over 40 independent DNS implementations, while some implementations have over 20 versions. The methodology used to identify individual nameserver implementations is based on "borderline" protocol behaviour. The DNS protocol offers a multitude of message bits, response types, opcodes, classes, query types and label types in a fashion that makes some mutually exclusive while some are not used in a query messages at all. Not every implementation offers the full set of features the DNS protocol set currently has. Some implementations offer features outside the protocol set, and there are implementations that do not conform to standards.

Scid is a chess database application; with it you can browse databases of chess games, edit games and search for games by various criteria. Scid uses its own special three-file database format which is very compact and fast, but it can convert to and from the standard PGN (Portable Game Notation) format. Scids PGN window displays the text of the current game in PGN format. You can use Scid to add chess games to a database, using the keyboard or mouse to enter moves. You can also use Scid as a PGN file browser, by pasting PGN text into Scids Import window or by opening a PGN file in Scid. However, PGN files cannot be edited by Scid (it opens them read-only) and they use more memory and are slower to load, so for large PGN files it is recommended that you create a Scid database from them first with the pgnscid utility.

Jelly is an XML based scripting engine. The basic idea is that XML elements can be bound to a Java Tag which is a Java bean that performs some function. Jelly is totally extendable via custom actions (in a similar way to JSP custom tags) as well as cleanly integrating with scripting languages such as Jexl, Velocity, pnuts, beanshell and via BSF (Bean Scripting Framework) languages like JavaScript & JPython. Jelly uses an XMLOutput class which extends SAX ContentHandler to output XML events. This makes Jelly ideal for XML content generation, SOAP scripting or dynamic web site generation. A single Jelly tag can produce, consume, filter or transform XML events. This leads to a powerful XML pipeline engine similar in some ways to Cocoon.