Implicit Parallelism in Capsule-oriented Program Design
Table of Contents
- Programming Guide Overview
- Motivation
- Getting Started
- Capsule-oriented Design
- Panini Language
- Implicit Parallelism
- Installing and Running the Panini compiler
- Profiling Panini Programs
- Technical Publications
- FAQ
Examples
Applicability of Capsules
In coarse-grained concurrent applications, such as the simplified Asteroids game illustrated in the previous chapter, the main motivation is not necessarily to achieve parallel execution but rather to correctly and safely model components that are "logically autonomous". These kinds of asynchronous, event-driven systems are the obvious candidates for capsule-oriented design. However, the capsule abstraction also adapts easily to other styles of parallel programming, while retaining Panini's advantages of abstracting away the concurrency control mechanisms and ensuring data confinement.
UNDER CONSTRUCTION FOR 0.9.2: Check back after 08/05/2013.
Master-Worker Pattern
Leader-Follower Pattern
Pipeline Pattern
Distributor Pattern
Page last modified on $Date: 2013/08/03 14:08:35 $