Free content caching software for linux

Content Dispatcher project will dispatch content over many plone sites in one click.

Let a content to be dispatch over many plone sites in one click.

ContentFeeder - A library used for assembling content feeds. RSS 2.0 is currently the only format supported, but can easily be extended to handle more.
ContentFeeder_RSS2 is the class name to instantiate to create RSS 2.0 feeds.
Example:
require(ContentFeeder.class.php);
$rss =& new ContentFeeder_RSS2;
Enhancements:
- change default character set to UTF-8
- change default escapement to none
- add escape type of none
- add setDefaultEscapeType()

Contelligent is a J2EE content management system that is targeted at developers and integrators. Contelligent provides an advanced package mechanism for development and deployment of Contelligent projects and extensions.
Contelligent implements a component based approach that allows reuse of existing content, layout, and application logic in various contexts and for new unplanned needs.
Main features:
- J2EE compliance,
- sophisticated content management and maintenance,
- easy and scalable content integration,
- dynamic personalisation based on user, roles and preferences,
- Integration of third party (legacy) application,
- guided separation of Content, Layout and Businesslogic
- high performance caching and dynamic page rendering.
Enhancements:
- This release is focused on adding small, useful features to the Web site related functionality, such as queries and menu components.
- The built-in bookmark system now supports bookmark folders.

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.

RtspProxy is a proxy server for multimedia streaming services based on the RTSP protocol.
The current version is a complete rewrite from scratch in Java of previous versions based on C++. The goal is to build a robust and scalable system usable in production environment.
The proxy is based on an asynchronous network framework, Apache MINA , which is built on Java NIO. This framework does permit to RtspProxy to handle high loads and concurrent users.
RTSP Caching Proxy is a proxy server that works with the RTSP protocol in multimedia streaming reproduction. RTSP (Real Time Streaming Protocol) is an emerging protocol for "session initiation" scopes, its purpose is to establish the conditions of an audio-video streaming session. The streaming data is then sent over other channels using other protocol such as RTP (Real Time Protocol).
Using a RTSP proxy does permits to access multimedia content without the need of being directly connected to the internet, for example being behind a corporate firewall.
Enhancements:
- A preliminary implementation of the IP address and host name filter was added.
- The Windows startup script was fixed.
- Session data is properly cleared when a session is closed.
- Only a UDP port pair is used for all RTP/RTCP packet handling and sending for all the connected clients.

Ciberia is a free blog aggregator, or content federator, that allows anyone to create a "Ciberpunk.com style" site in just five minutes.

You only need to have PHP installed on your server, and can change the appearance with CSS.

Instructions for installing Ciberia:

1. In data/uris_ciberguests.php and data/uris_members.php files, write the proper URIs from the blogs feeds
from member and guest blogs (left and right columns respectively), the path in the server from the install directory
and the e-mail adress where readers can write you.
2. In /graphics directory, save the pictures of members and guests as member_1.png, member_2.png ... and guest_1.png
etc. just in the same order you saved the URIs in step 1. We recommend 50x60 pixels.
3. Upload it all to your server and check that directories have write permission only for the program, not for the readers.
Be careful also with update.php: readers should have read permission only for that file.
4. Run install.php from your browser by typping http://www.yourdomain.any/install.php in the direction bar.
5. Dont forget to delete install.php after installation is finished!
6. Personalize style.css to modify the final view of the website. If you want to add banners or sections, you will must modify update.php

How Ciberia works:

The program updates its cache every 10 minutes, dont panic if your post does not appear inmediately on front.

Xitnalta Content Management System (xcms) provides a virtual filesystem library to deal with content from different sources (a real filesystem, a database, etc.) and in different formats.

Xitnalta Content Management Systems goal is to provide yet another way to access and manage data both locally and over the Internet.