Free robin hood costumes software for linux

OSCache is a high performance J2EE caching solution that can cache portions of JSP pages, entire HTTP responses (including dynamically generated images), and arbitrary Java objects.
OpenSymphony Cache can provide your J2EE application with huge performance gains and graceful error tolerance (e.g., in the event of a DB failure, cached content is served).
Fast in-memory caching
OSCache allows you to execute dynamic content periodically (eg every 30 minutes) rather than every request and store the result in memory. Each further request is served directly from the memory cache, resulting in dramatic speed increases.
The cache is keyed programmatically. This means you can calculate a cache key that works for your situation. For example an ecommerce site might use product ID as keys, or content site might use an article date and article ID combination.
The cache is stored in standard scopes that any JSP programmer is familiar with (application or session). The session scope allows you to have different cached content per user. This is one unlike any other caching system weve ever seen.
Persistent on-disk caching
OSCache can also write the cache to disk. This provides caching across server restarts, and caching of datasets that do not fit into memory. Caching can be configured to use memory or file caching, or a combination of both.
If you want to persist the cache to somewhere other than disk, you can plug in a custom PersistenceListener. This allows you to persist the cache to anywhere (for example to a database via JDBC or to LDAP via JNDI).
When using both disk caching and memory caching. It is possible to limit the cache size to avoid using too much memory but let disk cache unlimited, resulting in browser style complementary disk cache. When cached objects are removed from memory, they are still on disk. If the item is needed again and it is not expired the cache file will be used. This also gives fault tolerance if the server crashes.
Persistence can also be switched to overflow mode using the property oscache.persistence.overflow.only. This changes the default behavior (of persisting every cache entry when there is a listener) to only persist when the memory cache capacity has been reached.
Excellent Performance
Written with performance in mind.
Mulitple cache requests can be handled concurrently.
Only one requesting thread needs to update an expired cache entry even if multiple threads are requesting it simultaneously. Other threads can be configured to either receive the recently-expired object, or block until the cached object is updated. Similarly, when a new entry is being added to the cache, other threads requesting that entry will block until it is ready rather than run off and race to build the same object. In a high load environment this can provide enormous performance benefits.
Automatically takes advantage of JRE 1.4 or higher if available.
Clustering support
OSCache can easily be configured to cluster across multiple boxes. This provides both scalability and failover support without any changes required in your caching code.
Flexible Caching System
OSCache allows you to cache portions of JSP pages, arbitrary Java objects, and even entire servlet responses.
Cache capacity can be set allowing you to limit the number of cached objects.
Multiple caching algorithms are supported such as LRU (Least Recently Used), FIFO (First In First Out), or unlimited. It is also possible to plug in your own custom algorithm.
You are given a huge amount of control over the way cached objects expire. Objects can be cached indefinitely, expired once they reach a certain age, or expired based on a cron expression. Programmatic flushing is also possible, and if that is still not enough pluggable RefreshPolicies allow custom refresh strategies.
Cached objects can be grouped together however you like, allowing for powerful management of cached data. This is an extremely useful feature that is far more powerful than what other caching solutions typically offer (such as the flushing of cache keys that match a particular pattern).
Fully event driven! OSCache fires events for various happenings under the hood such as cache entry events (adding, updating, flushing and removing) and cache accesses (hit, stale hit and miss). It is easy to add your own event handlers.
Multiple caches can be created, each with their own unique configuration.
Simple JSP Tag Library
The tag library to perform and control the caching is very simple. See the Tag Reference for more information.
Caching Filter
A Servlet 2.3 Filter allows for caching of entire pages and generated binary files (like dynamically created images or PDF files).
Comprehensive API
For the ultimate control, OSCache can be used through its straightforward API. You can instantiate, configure and control multiple caches programmatically. It would be possible for example to create one small in-memory cache that held currency conversion rates and was updated daily at 2am, while another cache could be purely disk based and used for holding dynamically created images.
Exception Handling
OSCache provides a way for your site to gracefully tolerate errors. This is not error prevention, rather if an error occurs it should not stop your site from functioning. For example if your database goes down, normally your product descriptions will not be browsable. Using OSCache you can cache those descriptions so you can still browse them.
Cache Flushing
Flushing of caches can be controlled via JSP Tags, so these functions can easily be built into your administration interface.
There is programmatic control over what caches are flushed (eg all caches or just a particular scope).
Cached objects can be expired in a number of ways. Objects can be told to expire once they reach a certain age, or, through the use of cron expressions, on particular dates and/or times (eg it is trivial to make an object expire every weekday at 3am). If this is not enough, you can expire objects programmatically as required, or plug in your own custom RefreshPolicy class that can dynamically decide when an object should be flushed.
Entire groups of objects can be easily flushed from the cache. For example suppose you were caching product data as well as entire pages of your website. When a product was updated, you could flush not just the product object but also all the pages that contain information about that product. No more waiting for the cached objects to expire before the updated content shows up on your site!
Portable caching
Pure Java, this means it is platform independent.
OSCache is compliant with Servlet 2.3 and JSP 1.2 standards, which means it should work in the latest generation of servlet containers and application servers.
i18n Aware
The caching is i18n aware and supports all encodings.
Solid Reputation
Thousands of downloads, hundreds of users on the mailing list.
Comprehensive JUnit test suite that covers every aspect of OSCache, including a web stress test and various concurrent cache access scenarios. To back this up, the kind folks at Cortex have supplied us with a Clover license to provide detailed code coverage analysis of our unit tests.
We have solid issue tracking using JIRA to keep track of any feature requests, bug reports and development progress. JIRA is provided courtesy of Atlassian.
Enhancements:
- CRON expressions to expire content at specific dates and/or times.
- Pluggable EntryRefreshPolicy.
- Reduced memory consumption.
- Faster disk persistence.
- DiskPersistenceListener deadlocks are avoided if a process has no rights to delete the cache file.
- There is a new JSP tag _addgroups_, and an interface to get a list of the cache event listeners.
- The commons collection dependency has been removed.
- Java 1.3 support has been dropped.

Yahoo::Search::Request is a container object for a Yahoo! Search request. (This package is included in, and automatically loaded by, the Yahoo::Search package.)

Package Use

You never need to use this package directly -- it is loaded automatically by Yahoo::Search.

Object Creation

In practice, this class is generally not dealt with explicitly, but rather implicitly via functions in Yahoo::Search such as Query and Links, which build and use a Request object under the hood.

You also have access to the Request object via Request() method of resulting Response and Result objects.

To be clear, Request objects are created by the Request() method of a Search Engine object (Yahoo::Search).

Xyria:DNSd is an high performance DNS server that supports only the most important features and resource records while being extremely fast and secure.
Xyria:DNSd peoject also supports round-robin load balancing.
Main features:
- extemely fast implementation (main target)
- very secure
- ip-address based listen()ing
- supporting IPv6 addresses and resource records
- load ballancing via round robbin
- running under an low-privileged UID & GID
- running under little endian systems: (at least) Linux, Solaris, OpenBSD
- nice configuration syntax/easy to configure
- DNSd able to forward querys
- DNSd can run as caching only-server
Enhancements:
- The database was modified. Now DNSd uses a hashed array of pointers to binary trees including single linked lists for double valued hashes.
- It sorts the zones (by TTL) by itself (the admin doesnt has to care in which order he has to place the zones in the config file).
- Some code cleanup and a small bugfix are also included.

Protoscope is a utility that aids Web developers by revealing the HTTP communication in their own applications. It is a nice tool for Web developers who want to "look under the hood" as they develop.

Protoscope is somehow like a HTTP proxy serve and runs like it. It expects to receive HTTP requests from a Web client (such as your Web browser) that is configured to use a proxy.

Note: Most Web browsers allow you to conveniently select a proxy server to use, and the Protoscope Web site will eventually have instructions on how to achieve this for those who need assistance. If you write a HOWTO for configuring a particular browser to use Protoscope, I will gladly link to it. See http://shiflett.org/projects/protoscope/ for more information.

Protoscope forwards the HTTP requests to the origin server just as a proxy would and replies to the Web client with the servers responses. This is all transparent to the Web browser, and it does not affect your browsing in any way.

The difference is that Protoscope logs all communication in the log file that you configure it to use, so that you can examine this log file (or tail it) to examine the HTTP transactions.

In addition, version 0.7.1 added the option to have this information embedded into the HTML document itself. This makes debugging and related tasks extremely efficient while you are developing, and it can even help to avoid having to view source and risk the page being expired from cache or any other annoyances. Simply scroll to the bottom of the page anytime there is a question about the current
transaction. This is the recommended way to use Protoscope.

Aranha is an application that uses an XML-RPC layer to retrieve information from one or more servers. The type of information gathered is implemented via plugins, and can be displayed or archived in several different ways.

The data is gathered in Round Robin Databases (integrated with rrdtool) and can be accessed using a XUL interface available from the system. Plugins are very easy to write.

Configuration

To configure this module, either pass specific configuration values to
Makefile.PL like this:

perl Makefile.PL CONFIG_VAR="config val"
or
edit the %DEFAULTS variable on the toplevel Makefile.PL

Installation

To install this module type the following:

perl Makefile.PL
make
make test
make install

vHost is a one-step solution for all virtual hosting needs. It enables a Linux/BSD server with single or multiple IP addresses to function as unlimited virtual hosts with HTTP, FTP, SMTP, POP3, IMAP, and other virtual services extendible via modules.
vHost comes with both a command-line interface and a web-based GUI ("control panel"), offering maximum control to a domains owner while relieving the system administrator of most routine administration tasks. Other major features include four levels of login, comprehensive quota control, and built-in clustering capability.
Main features:
- Supports all major Linux distros, and FreeBSD, NetBSD.
- Integrated install/upgrade module provides effortless one-step install and upgrade from any old version.
- Retains all previous system configurations while upgrading in order to ensure zero downtime.
- Clean virtual host file system follows *nix conventions.
- Virtual user home/web space.
- Integrated web-based FTP client for virtual users as well as host owners.
- All operations available in both command-line and web-based GUI ("control panel").
- Modularized architecture allows for arbitrary features and virtual services extended by modules.
- Four levels of login and security: root, vroot ("reseller"), host owner, and virtual user.
- Comprehensive quota control: disk space limit, inbox size limit, per-owner host limit, per-host user limit.
- Built-in clustering capability supports DNS round-robin clustering and distributed host/DNS.
- Automatic local and remote DNS setup.
- Automatic IP address aliasing and management for multiple-IP systems.
- Supports host alias and user alias.
- Built-in log rotation, easy exclusion of logs from rotation.
- Optional email "catch-all".
- Built-in "POP before SMTP" relay support.
- True virtual webmail per virtual host.
- Virtual host webstats.
- Command logging.
- Optional per-host and per-owner profiles for fine-grained system configuration.
- Easy system migration with command --cphost.
- No database backend required.
Enhancements:
- This is a major release with a minor version number increment (version 4.0 is planned for a new Web GUI).
- Changes include an integrated Web-based FTP client, a virtualization module for OpenWebmail, the new commands --addmydb/--delmydb, virtual user ".forward" support, improved SELinux support, improvements for clustering/distributed systems, numerous other fixes and enhancements, and documentation.

SuperShaper-SOHO is a traffic shaping setup for DSL connections which prioritizes VoIP and interactive traffic and makes sure P2P traffic doesnt saturate your uplink.
IPCop 1.3 and newer is known to work and is the preferred deployment setup. Firstly, be sure to disable the integrated traffic shaper in IPCop 1.4 if you use SuperShaper-SOHO.