Download JAR files tagged by strategies with all dependencies

How many classes does it take to make a cache? 60? 80? You might think so if you look at the other caches on the market. Ashkay is a streamlined, simple cache that in many ways is more powerful than the other mainstream caches. Ashkay is a strategy based caching tool. In most cases, you might be using a configuration file to tell the cache what rules it should obey. Or, you might just be setting properties on the cache. I have never liked this model as it limits me, the user of the cache to strategies the developer decided were important. Instead, Ashkay lets you choose the strategy(ies) to use when caching certain objects. Of course, a few of the most handy strategies are pre-packaged, but implementing a new one is a simple as can be. Ashkay is a fork of <a href="http://xot.sf.net">xot</a> caching code. Made more sense on its own.

Sirix is a versioned, treebased storage system. It provides an ID-less diff-algorithm to import differences between two versions. Furthermore an ID-based diff-algorithm facilitates the comparison of versions stored within Sirix. A GUI with several visualizations for comparing these versions visually is available to aid an analyst. Versions are stored using well known versioning strategies (full, incremental, differential). The architecture is especially well suited for flash-disks because of a COW-principle. In the future we aim to provide throughout security as well as a replaced page-structure to speedup our architecture. A brackit(.org) binding will enable XQuery and the XQuery Update Facility. Temporal XPath axis and possibly diff-functions will help analysts to gain quick knowledge from the stored data.

Sirix is a versioned, treebased storage system. It provides an ID-less diff-algorithm to import differences between two versions (currently XML-documents). Furthermore an ID-based diff-algorithm facilitates the comparison of versions stored within Sirix. A GUI with several visualizations for comparing these versions visually is available to aid an analyst. Versions are stored using well known versioning strategies (full, incremental, differential). The architecture is especially well suited for flash-disks because of a COW-principle. In the future we aim to provide throughout security as well as a replaced page-structure to speedup our architecture. A brackit(.org) binding will enable XQuery and the XQuery Update Facility. Temporal XPath axis and possibly diff-functions will help analysts to gain quick knowledge from the stored data.

The boilerpipe library provides algorithms to detect and remove the surplus "clutter" (boilerplate, templates) around the main textual content of a web page. The library already provides specific strategies for common tasks (for example: news article extraction) and may also be easily extended for individual problem settings. Extracting content is very fast (milliseconds), just needs the input document (no global or site-level information required) and is usually quite accurate. Boilerpipe is a Java library written by Christian Kohlschütter. It is released under the Apache License 2.0. The algorithms used by the library are based on (and extending) some concepts of the paper "Boilerplate Detection using Shallow Text Features" by Christian Kohlschütter et al., presented at WSDM 2010 -- The Third ACM International Conference on Web Search and Data Mining New York City, NY USA.