directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1023871 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/1.4-interceptors.html
Date Mon, 15 Jan 2018 07:25:03 GMT
Author: buildbot
Date: Mon Jan 15 07:25:03 2018
New Revision: 1023871

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan 15 07:25:03 2018
@@ -1 +1 @@
-1821061
+1821128

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html Mon
Jan 15 07:25:03 2018
@@ -182,7 +182,7 @@
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
 <h1 id="14-interceptors">1.4 - Interceptors<a class="headerlink" href="#14-interceptors"
title="Permanent link">&para;</a></h1>
 <p><em>Interceptors</em> are functional layers inside the <em>DirectoryService</em>.
Each one of them are responsible for a specific task. They are ordered, and this order is
not to be changed.</p>
-<p>Each operation rceived by the <em>DirectoryService</em> will be processed
by various interceptors, one after the other, down to the backend, and again when the result
comes back to the caller. An <em>interceptor</em> can call the next <em>interceptor</em>,
whcih will be determinated by the position it has in the chain of <em>interceptors</em>,
or simply return. Note that calling the next <em>interceptor</em> does not require
that you know which one will be called.</p>
+<p>Each operation received by the <em>DirectoryService</em> will be processed
by various interceptors, one after the other, down to the backend, and again when the result
comes back to the caller. An <em>interceptor</em> can call the next <em>interceptor</em>,
whcih will be determinated by the position it has in the chain of <em>interceptors</em>,
or simply return. Note that calling the next <em>interceptor</em> does not require
that you know which one will be called.</p>
 <p>Some <em>Interceptors</em> can be disabled, some other can be enabled.
It's also possible to add some new one.</p>
 <p>All in all, they will handle operations from a specific functional aspect.</p>
 <h2 id="handled-operations">Handled operations<a class="headerlink" href="#handled-operations"
title="Permanent link">&para;</a></h2>



Mime
View raw message