Free hood nigga 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.

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.

xDash is a framework for application integration (EAI). xDash is using XMPP/jabber as the communication protocol and a set of agents. All the needed stuff is automatically generated from a CSV file, which can be comfortably edited in a spreadsheet editor.
xDash can be classified in marketing terms as:
- an Enterprise Application Integration (EAI) solution or
- an Enterprise Service Bus (ESB).
xDash is based on the concept of convergence between backend asynchronous messaging (like IBM MQSeries or JMS) and instant messaging (like IRC or Jabber).
Main features:
- You have to manage a fast integration project with little time and low budget;
- You are convinced, that integration has so many faces, that agile approach and flexible design are better than buying a "silver bullet" from big names;
- You are convinced, that integration is rather a continuous, never-ending process than a single act of some software implementation;
- You would like to concentrate on writing the integration logic in a well known environment and have no time to learn myriads of new options and APIs with little reuse;
- You need an open human readable communication protocol (XML), where you can see what is going on under the hood;
- You need a free open source multiplatform information bus for publish/subscribe integration;
- You are interested in a ground-breaking project dealing with the convergence of instant and backend asynchronous messaging.
What is the core of the xDash?
xDash is at basis every sort of an integration project, which sticks to the following rules:
- Communication over Jabber protocol;
- The extension of the message type to type=job for all relevant messages;
- The message sending schema, in which always participate a message sender, a message receiver and a message archivist ("integration chain").
- For each sort of event, triggering a Sender, there is only one integration chain defined on the server by a set of Jabber IDs and forwarding rules ("Who knows whom" schema).
- The client software of Sender and Receiver knows nobody but the Archivist.
- The jabber server forwards Senders messages sent to the Archivist, additionally to the Receivers.

DTDParse project is a tool for parsing SGML and XML DTDs.

The primary motivation for writing it was to provide a framework for building documentation for DTDs, but other applications are easy to imagine.

DOLFIN project is the C++ interface of FEniCS, providing a consistent PSE (Problem Solving Environment) for solving ordinary and partial differential equations.
Main features:
- Simple, consistent and intuitive object-oriented API
- Automatic and efficient evaluation of variational forms through FFC
- Automatic and efficient assembly of linear systems
- Support for general families of finite elements, including continuous and discontinuous Lagrange finite elements of arbitrary order on triangles and tetrahedra through FIAT
- Support for arbitrary mixed elements, including Taylor-Hood
- High-performance parallel linear algebra through PETSc with simple C++ wrappers
- Triangular and tetrahedral meshes, including adaptive mesh refinement and mesh hierarchies
- Multi-adaptive mcG(q)/mdG(q) and mono-adaptive cG(q)/dG(q) ODE solvers
- Support for a range of output formats for post-processing, including DOLFIN XML, MATLAB, Octave, OpenDX, GiD, Tecplot and Paraview/VTK
- SWIG-generated Python interface PyDOLFIN (experimental) in addition to the standard C++ interface

UT2004: SAS is an UT2004 Mod that focuses on the three main SAS units around the world. SAS focuses on the three main SAS units around the world, the British SAS, the Australian SASR and the New Zealand NZSAS who all perform counter-terrorism, operating deep behind enemy lines, gathering intelligence and other duties in various countries.

Their main advesary is OpFor that stands for Opposing Forces who are a collection of the enemies the SAS have faced in past and present times. Their ranks are comprised of regular military, guerilla, terrorist and para-military groups.

Players can choose their in-game player model from a variety of uniforms based on its real world counterpart. From the environment based camouflage patterns of desert, woodland, and jungle to counter-terrorism kits players will have a wide variety of choices. Certain player models feature unique attributes such as body armor, anti-flash hoods and camouflage.

Weapon selection in SAS is done through a loadout system where you can select a primary weapon where your choices are a submachine gun, assault rifle, shotgun, sniper rifle or light machine gun. Secondary weapons include pistols while other parts of the loadout allow you to chose three different grenade types and a knife. Weapons in SAS can kill very easily, some with just a single three round burst.