X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=PPI%2FMainpage.dox;h=cd89148ad8ff0e223444881ddf3578be50723cdf;hb=a479735a65e334af538b895f182f8efd36a541c5;hp=cd3167e7a9b2ee96a67b9ede86b544977e70621b;hpb=fa368bbbcb79a9aad8daf7cb25a9adee8270d1b8;p=senf.git

diff --git a/PPI/Mainpage.dox b/PPI/Mainpage.dox
index cd3167e..cd89148 100644
--- a/PPI/Mainpage.dox
+++ b/PPI/Mainpage.dox
@@ -61,6 +61,7 @@
     <li>\ref ppi_connections</li>
     <li>\ref ppi_throttling</li>
     <li>\ref ppi_events</li>
+    <li>\ref ppi_run</li>
     <li>\ref ppi_flows</li>
     </ol>
     </div>
@@ -365,6 +366,19 @@
 
     \see senf::ppi::EventDescriptor
 
+    \section ppi_run Running the network
+
+    After the network has been set up, senf::ppi::run() is called to execute it. This call will only
+    return after all data has been processed. The PPI knows this, when no events are enabled any
+    more. Without events, nothing will happen any more since it is the events which drive the
+    PPI. Therefore the PPI surmises, that all data has been processed and returns from
+    senf::ppi::run().
+
+    This works very well with automatic throttling. When no data is available to be processed any
+    more and no more data can be expected to arrive (for Example since data has been read from a
+    file which is now exhausted) all events will be disabled automatically via trhottle
+    notifications and so signal that any processing should stop.
+
     \section ppi_flows Information Flow
 
     The above description conceptually introduces three different flow levels: