felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pde...@apache.org
Subject svn commit: r1665537 - /felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/reference/thread-model.mdtext
Date Tue, 10 Mar 2015 13:30:25 GMT
Author: pderop
Date: Tue Mar 10 13:30:25 2015
New Revision: 1665537

URL: http://svn.apache.org/r1665537
Fixed formatting.


Modified: felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/reference/thread-model.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/reference/thread-model.mdtext?rev=1665537&r1=1665536&r2=1665537&view=diff
--- felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/reference/thread-model.mdtext
+++ felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/reference/thread-model.mdtext
Tue Mar 10 13:30:25 2015
@@ -2,7 +2,7 @@ Title: Apache Felix Dependency Manager -
 This section gives a brief overview of the default thread model used by Dependency Manager,
and also explains how to start and handle components concurrently.
-# Default Thread Model
+## Default thread model
 By default, Dependency Manager uses a lock-free/single thread model:
@@ -23,7 +23,7 @@ The following diagram illustrates the th
 <img src="./diagrams/serial-queue.png" alt="Serial Queue" style="width: 600px"/>
-# Enabling parallelism with a ComponentExecutorFactory
+## Enabling parallelism with a *ComponentExecutorFactory*
 As described above, all the external events that influence the state of a given component
are handed by jobs scheduled in the Serial Queue of the Component, and the jobs are getting

 executed serially by a single "master" thread. So usually, bundles are started from a single
thread, meaning that all Components are then activated synchronously.
@@ -48,7 +48,7 @@ Notice that if the ComponentExecutorFact
 "!" prefix, in order to indicate that those components must not wait for a ComponentExecutorFactory
service (since they are part of the ComponentExecutorFactory implementation !). 
-### Examples for the usage of the "org.apache.felix.dependencymanager.parallel" property:
+### Examples usage of the *org.apache.felix.dependencymanager.parallel* property:
          -> means all components must be cached until a ComponentExecutorFactory comes

View raw message