You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by np...@apache.org on 2018/10/09 09:43:25 UTC
[sling-site] branch asf-site updated: publishing #25 changes
This is an automated email from the ASF dual-hosted git repository.
npeltier pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new ff604d8 publishing #25 changes
ff604d8 is described below
commit ff604d838ba63e7bf883b2b13a0c7c38a766dfee
Author: Nicolas Peltier <np...@nicolass-mbp.eur.adobe.com>
AuthorDate: Tue Oct 9 11:43:23 2018 +0200
publishing #25 changes
---
documentation/bundles/sling-pipes.html | 4 ++--
documentation/bundles/sling-pipes/logical.html | 10 +++++-----
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/documentation/bundles/sling-pipes.html b/documentation/bundles/sling-pipes.html
index 2dd58fa..54ae299 100644
--- a/documentation/bundles/sling-pipes.html
+++ b/documentation/bundles/sling-pipes.html
@@ -100,7 +100,7 @@
<p>With Sling Pipes, what you need to develop, and what is readable by another developer is</p>
<pre><code> plumber.newPipe(resolver).$("foo/bar").write("id",3).build("/etc/demo")
</code></pre>
-<p>this is enough to persist a pipe in <code>/etc/demo</code> that is executable as http, java, groovy console script, or JMX. You can make it monitor it with JMX, logs, http, you'll have dry run possibility of that execution for example, or asynchronous execution. You could also use a pipe to create a java-free json or csv servlet, or a list component whose list possibilities are pipes accessed through the <code>PipeModel</code></p>
+<p>this is enough to persist a pipe in <code>/etc/demo</code> that is executable as http, java, groovy console script, or JMX. You can monitor it with JMX, logs, http, you'll have dry run possibility of that execution for example, or asynchronous execution. You could also use a pipe to create a java-free json or csv servlet, or a list component whose list possibilities are pipes accessed through the <code>PipeModel</code></p>
<p>you can check some introductions at different adaptTo presentations:</p>
<h2><a href="#adaptto-introductions" name="adaptto-introductions">AdaptTo introductions</a></h2>
<p>some presentations were made at the adaptTo conference, last two were:</p>
@@ -141,7 +141,7 @@
</ul></section></div></div>
<div class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Nicolas Peltier</span> on <span class="comment">Mon Oct 8 17:09:17 2018 +0200</span>
+ Last modified by <span class="author">Stefan Popescu</span> on <span class="comment">Mon Oct 8 19:28:20 2018 +0300</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p><p>
diff --git a/documentation/bundles/sling-pipes/logical.html b/documentation/bundles/sling-pipes/logical.html
index 5c59130..0137f90 100644
--- a/documentation/bundles/sling-pipes/logical.html
+++ b/documentation/bundles/sling-pipes/logical.html
@@ -112,11 +112,11 @@
<h4><a href="#manifold" name="manifold">Manifold</a></h4>
<p>allows parallel execution of the sub pipes listed in configuration</p>
<ul>
- <li><code>sling:resourceType</code> is <code>slingPipes/filter</code></li>
+ <li><code>sling:resourceType</code> is <code>slingPipes/manifold</code></li>
<li><code>conf</code> node contains child pipes' configurations, that will be configured in the order they are found (note you should use sling:OrderedFolder)</li>
- <li><code>queueSize</code> size of the merged resource queue,</li>
- <li><code>numThread</code> thread pool size for the execution of the subpipes</li>
- <li><code>executionTimeout</code> execution time out for each sub pipe</li>
+ <li><code>queueSize</code> size of the merged resource queue, default is 10000</li>
+ <li><code>numThread</code> thread pool size for the execution of the subpipes, default is 5 - resource output will be ordered randomly; setting it to 1 will guarantee serial execution with predictable output order (i.e. the first subpipe resources will be exhausted before the second subpipe resources are output etc.); setting numThreads to 1 will have similar effects to using a container pipe, with the notable exception of output termination: whereas a container pipe chains sub pipe [...]
+ <li><code>executionTimeout</code> execution time out for each sub pipe; given in seconds; default is 24h</li>
</ul>
<h3>FilterPipe (<code>grep(conf)</code>)</h3>
<p>outputs the input resource if its matches its configuration</p>
@@ -141,7 +141,7 @@
</ul></section></div></div>
<div class="footer">
<div class="revisionInfo">
- Last modified by <span class="author">Nicolas Peltier</span> on <span class="comment">Mon Oct 8 17:09:17 2018 +0200</span>
+ Last modified by <span class="author">Stefan Popescu</span> on <span class="comment">Mon Oct 8 19:28:20 2018 +0300</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p><p>