Remove trailing spaces

Author: pcanal

doc/v600/Trailer.md

@@ -1,4 +1,4 @@
 <center>
-[ROOT page](http://root.cern.ch) - [Class index](http://root.cern.ch/root/htmldoc/ClassIndex.html) - 
+[ROOT page](http://root.cern.ch) - [Class index](http://root.cern.ch/root/htmldoc/ClassIndex.html) -
 [Top of the page](#TopOfPage)
 </center>

documentation/HttpServer/HttpServer.md

@@ -1,14 +1,14 @@
 # HTTP server in ROOT
 
-Idea of such server – provide direct access to the different data 
-from running ROOT application. Any object can be streamed at the moment 
-when request is coming and delivered to the browser. 
-Main benefit of such approach – one do not need to create any temporary ROOT files for such task. 
+Idea of such server – provide direct access to the different data
+from running ROOT application. Any object can be streamed at the moment
+when request is coming and delivered to the browser.
+Main benefit of such approach – one do not need to create any temporary ROOT files for such task.
 
 ## Starting HTTP server
 
 To start http server, at any time  create instance
-of the **`THttpServer`** class like: 
+of the **`THttpServer`** class like:
 
 ``` {.cpp}
 serv = new THttpServer("http:8080");
@@ -17,9 +17,9 @@ serv = new THttpServer("http:8080");
 This will starts civetweb-based http server with http port 8080.
 Than one should be able to open address "http://localhost:8080"
 in any modern browser (IE, Firefox, Chrome, Opera) and browse objects,
-created in application. By default, server can access files, canvases 
+created in application. By default, server can access files, canvases
 and histograms via gROOT pointer. All such objects can be displayed with
-JSRootIO graphics. 
+JSRootIO graphics.
 
 At any time one could register other objects with the command:
 
@@ -31,13 +31,13 @@ serv->Register("graphs/subfolder", gr);
 
 If objects content is changing in the applicaion, one could
 enable monitoring flag in the browser - than objects view will be regularly updated.
-   
+
 
 ## Configuring user access
 
-By default http server is open for anonymous access. 
+By default http server is open for anonymous access.
 One could restrict access to the server only for authenticated users.
-First of all, one should create password file, using **htdigest** utility.  
+First of all, one should create password file, using **htdigest** utility.
 
 ``` {.sh}
 [shell] htdigest -c .htdigest domain_name user_name
@@ -56,7 +56,7 @@ After that browser will automatically request to input name/password for domain
 
 ## Using FastCGI interface
 
-FastCGI is a protocol for interfacing interactive programs with a web server like 
+FastCGI is a protocol for interfacing interactive programs with a web server like
 Apache, lighttpd, Microsoft ISS and many others.
 
 When starting THttpServer, one could specify:
@@ -79,12 +79,12 @@ Example of configuration file for lighttpd server is:
  )
 ```
 
-In this case, to access running ROOT application, one should open 
+In this case, to access running ROOT application, one should open
 following address in the browser:
     http://lighttpd_hostname/remote_scripts/root.cgi/
 
 In fact, FastCGI interface can run in parallel to http server.
-One just call: 
+One just call:
 
 ``` {.cpp}
 serv = new THttpServer("http:8080");
@@ -96,9 +96,9 @@ One could specify debug parameter to be able adjust FastCGI configuration on the
 ``` {.cpp}
 serv->CreateEngine("fastcgi:9000/none?debug=1");
 ```
- 
-All user access will be ruled by web server - 
-for the moment one cannot restrict with fastcgi engine. 
+
+All user access will be ruled by web server -
+for the moment one cannot restrict with fastcgi engine.
 
 
 ## Integrate with existing applications
@@ -112,8 +112,8 @@ Central point of integration - when and how THttpServer get access to data from
 By default it is done during gSystem->ProcessEvents() call - THttpServer uses synchronous timer,
 which is activated every 100 ms. Such approach works perfectely when running macros in interactive ROOT shell.
 
-If application runs in compiled code and does not contains gSystem->ProcessEvents() calls, 
-two method are available. 
+If application runs in compiled code and does not contains gSystem->ProcessEvents() calls,
+two method are available.
 
 ### Asynchrounous timer
 
@@ -123,7 +123,7 @@ First method is to configure asynchronous timer for the server like:
 serv->SetTimer(100, kFALSE);
 ```
 
-Than timer will be activated even without gSystem->ProcessEvents() method call. 
+Than timer will be activated even without gSystem->ProcessEvents() method call.
 Main advantage of such method that application code can be used as it is.
 Disadvantage - there is no control when communication between server and application is performed.
 It could happen just in-between of **`TH1::Fill()`** call and histogram object may be incomplete.
@@ -132,7 +132,7 @@ It could happen just in-between of **`TH1::Fill()`** call and histogram object m
 ### Explicit call of THttpServer::ProcessRequests() method
 
 Second method is preferable - one just insert in the application
-regular calls of the THttpServer::ProcessRequests() method. Like:  
+regular calls of the THttpServer::ProcessRequests() method. Like:
 
 ``` {.cpp}
 serv->ProcessRequests();
@@ -148,10 +148,10 @@ serv->SetTimer(0, kTRUE);
 
 ## Data access from command shell
 
-Big advantage of http protocol that it supported not only in web browsers 
-but also in many other applications. 
-One could directly use http requests to access 
-ROOT objects and data members from any kind of scripts. 
+Big advantage of http protocol that it supported not only in web browsers
+but also in many other applications.
+One could directly use http requests to access
+ROOT objects and data members from any kind of scripts.
 
 If one starts server and register object like:
 
@@ -185,7 +185,7 @@ One could access also class members of object like:
 ``` {.sh}
 [shell] wget http://localhost:8080/Objects/subfolder/obj/fTitle/root.json
 ```
-  
+
 Result will be: "title".
 
 If access to the server restricted with htdigest method,
@@ -199,10 +199,10 @@ Command will look like:
 Following requests can be performed:
    * root.bin  - 20-byte header and zipped binary TBuffer content
    * root.json - ROOT JSON representation for object and objects members
-   * root.xml  - ROOT XML representation   
-   * root.png  - PNG image   
-   * root.gif  - GIF image   
-   * root.jpeg - JPEG image   
+   * root.xml  - ROOT XML representation
+   * root.png  - PNG image
+   * root.gif  - GIF image
+   * root.jpeg - JPEG image
 
 For images one could specify h (height), w (width) and opt (draw) options. Like:
 

documentation/HttpServer/title.txt

@@ -1,2 +1,2 @@
-% HTTP Server 
+% HTTP Server
 % Sergey Linev