svn commit: r1464401 - /sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext

[bd...@apache.org]

Author: bdelacretaz
Date: Thu Apr  4 09:43:11 2013
New Revision: 1464401

URL: http://svn.apache.org/r1464401
Log:
4 spaces for nested lists?

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext?rev=1464401&r1=1464400&r2=1464401&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/filters.mdtext Thu Apr  4 09:43:11 2013
@@ -38,24 +38,24 @@ Note on `INCLUDE` and `FORWARD` with res
 Filter processing is part of the Sling request processing, which may be sketched as follows:
 
 * *Request Level*:
- * Authentication
- * Resource Resolution
- * Servlet/Script Resolution
- * Request Level Filter Processing
+    * Authentication
+    * Resource Resolution
+    * Servlet/Script Resolution
+    * Request Level Filter Processing
 
 The first step of request processing is the *Request Level* processing which is concerned with resolving the resource, finding the appropriate servlet and calling into the request level filter chain. The next step is the *Component Level* processing, calling into the component level filters before finally calling the servlet or script:
 
 * *Component Level*:
- * Component Level Filter Processing
- * Call Servlet or Script
+    * Component Level Filter Processing
+    * Call Servlet or Script
 
 When a servlet or script is including or forwarding to another resource for processing through the `RequestDispatcher` (or any JSP tag or other language feature ultimately using a `RequestDispatcher`) the following *Dispatch* processing takes place:
 
 * *Dispatch*:
- * Resolve the resource to dispatch to if not already defined when getting the `RequestDispatcher`
- * Servlet/Script resolution
- * Call include or forward filters depending on the kind of dispatch
- * Call Servlet or Script
+    * Resolve the resource to dispatch to if not already defined when getting the `RequestDispatcher`
+    * Servlet/Script resolution
+    * Call include or forward filters depending on the kind of dispatch
+    * Call Servlet or Script
 
 As a consequence, request level filters will be called at most once during request processing (they may not be called at all if a filter earlier in the filter chain decides to terminate the request) while the component level, include, and forward filters may be called multiple times while processing a request.
 
@@ -113,4 +113,4 @@ Up to and including Sling Engine 2.1.0 s
 
 * Any `javax.servlet.Filter` service is accepted as a filter for Sling unless the `pattern` property used by the [Apache Felix HttpService whiteboard support]({{ refs.http://felix.apache.org/site/apache-felix-http-service.html#ApacheFelixHTTPService-UsingtheWhiteboard.path }}) is set in the service registration properties.
 * The `filter.scope` property is optional and supports the case-sensitive values `request` and `component`.
-* Filter ordering is defined by the `filter.order` property whose default value is `Integer.MAX_VALUE` where smaller values have higher priority over higher values.
+* Filter ordering is defined by the `filter.order` property whose default value is `Integer.MAX_VALUE` where smaller values have higher priority over higher values.
\ No newline at end of file