uid_domain: docs - removed trailing spaces

src/modules/uid_domain/doc/domain_api.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
    "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
 <section id="domain.api" xmlns:xi="http://www.w3.org/2001/XInclude">
@@ -15,7 +15,7 @@
 	module then you need to include the header file
 	<filename>domain_api.h</filename> and call
 	<function>load_domain_api</function> first.</para>
-	
+
 	<example>
 		<title>Calling <function>load_domain_api</function></title>
 		<programlisting>
@@ -32,7 +32,7 @@ if (load_domain_api(&amp;dom_api) != 0) {
 	<para>After that you can call function
 	<function>is_domain_local</function> whose pointer is stored in the
 	initialized data structure:</para>
-	
+
 	<programlisting>
 str tmp = STR_STATIC_INIT("mydomain.com");
 
@@ -44,4 +44,3 @@ if (dom_api.is_domain_local(&amp;tmp) == 1) {
 	</programlisting>
 </section>
 
-		

src/modules/uid_domain/doc/fifo.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
    "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
 <section id="domain.fifo" xmlns:xi="http://www.w3.org/2001/XInclude">
@@ -24,5 +24,5 @@
 	    cache memory.
 	</para>
     </section>
-    
+
 </section>

src/modules/uid_domain/doc/functions.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
    "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
 <section id="domain.functions" xmlns:xi="http://www.w3.org/2001/XInclude">

src/modules/uid_domain/doc/params.xml

@@ -1,13 +1,13 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
    "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
 <section id="domain.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
 	</sectioninfo>
-	
+
 	<title>Parameters</title>
-	
+
 	<section id="domain.db_url">
 		<title><varname>db_url</varname> (string)</title>
 		<para>
@@ -23,14 +23,14 @@ modparam("domain", "db_url", "mysql://ser:pass@db_host/ser")
 			</programlisting>
 		</example>
 	</section>
-	
+
 	<section id="db_mode">
 		<title><varname>db_mode</varname> (integer)</title>
 		<para>
 			Database mode. Value 0 means non-caching, 1
-		means caching is enabled. It 
+		means caching is enabled. It
 			is highly recommended to enable caching if you
-		want to use 
+		want to use
 			domain-level attributes.
 		</para>
 		<para>
@@ -43,7 +43,7 @@ modparam("domain", "db_mode", 0)   # Do	not use caching
 			</programlisting>
 		</example>
 	</section>
-	
+
 	<section id="domain_table">
 		<title><varname>domain_table</varname> (string)</title>
 		<para>
@@ -81,7 +81,7 @@ modparam("domain", "did_col", "did")
 			</programlisting>
 		</example>
 	</section>
-	
+
 	<section id="domain.domain_col">
 		<title><varname>domain_col</varname> (string)</title>
 		<para>

src/modules/uid_domain/doc/uid_domain.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
    "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
 <book id="uid_domain" xmlns:xi="http://www.w3.org/2001/XInclude">
@@ -40,7 +40,7 @@
 			the documentation. DID stands for "Domain IDentifier". In
 			traditional POST world the term DID has a different meaning
 			though. Please be aware that this is just pure coincidence.</para>
-			
+
 			<para>All domain names that belong to one virtual domain are
 			interchangeable. From SIP server's perspective there is no
 			difference between them. They can be used in SIP URIs
@@ -57,7 +57,7 @@
 			can use anything as long as it can be represented as string. The
 			only requirement is that the identifier of each virtual domain
 			must be unique.</para>
-		
+
 			<para>The following example illustrates how one virtual domain can
 			be represented. The iptel.org domain runs a public SIP
 			service. The users of the service can use SIP URIs of form
@@ -79,7 +79,7 @@ iptel
   +---213.192.59.75
 				</programlisting>
 			</example>
-			
+
 			<para>In the example above, we chose "iptel" as the unique
 			identifier for the virtual domain. This identifier is
 			permanent. It never changes. Over time we may change domain names
@@ -99,10 +99,10 @@ iptel
 +-------+-----------------+-------+
 | did   | domain          | flags |
 +-------+-----------------+-------+
-| iptel | iptel.org       |    33 | 
-| iptel | sip.iptel.org   |    33 | 
-| iptel | proxy.iptel.org |    33 | 
-| iptel | 213.192.59.75   |    33 | 
+| iptel | iptel.org       |    33 |
+| iptel | sip.iptel.org   |    33 |
+| iptel | proxy.iptel.org |    33 |
+| iptel | 213.192.59.75   |    33 |
 +-------+-----------------+-------+
 				</programlisting>
 			</example>
@@ -116,7 +116,7 @@ iptel
 			domain then joe will also be able to use the new domain name in
 			his SIP URI, without the need to change anything.</para>
 		</section>
-		
+
 		<section>
 			<title>Domain-level Configuration Attributes</title>
 			<para>In addition to a number of domain names, each virtual domain
@@ -128,7 +128,7 @@ iptel
 			different customers and each of the customers may have slightly
 			different configuration requirements. That's how domain-level
 			configuration attributes were born.</para>
-		
+
 			<para>Because the administrator of the SIP server seldom knows
 			configuration requirements in advance, we decided to implement a
 			generic solution and store all configuration options in named
@@ -143,7 +143,7 @@ iptel
 			configured for a particular user. In other words a domain level
 			attribute will only be effective if no user-level attribute with
 			the same name exists.</para>
-			
+
 			<para>Domain-level attributes are stored in a separate table. The
 			name of the table is domain_attrs and it is defined as follows:
 			</para>
@@ -154,11 +154,11 @@ iptel
 +-------+------------------+------+-----+---------+-------+
 | Field | Type             | Null | Key | Default | Extra |
 +-------+------------------+------+-----+---------+-------+
-| did   | varchar(64)      | YES  | MUL | NULL    |       | 
-| name  | varchar(32)      | NO   |     | NULL    |       | 
-| type  | int(11)          | NO   |     | 0       |       | 
-| value | varchar(255)     | YES  |     | NULL    |       | 
-| flags | int(10) unsigned | NO   |     | 0       |       | 
+| did   | varchar(64)      | YES  | MUL | NULL    |       |
+| name  | varchar(32)      | NO   |     | NULL    |       |
+| type  | int(11)          | NO   |     | 0       |       |
+| value | varchar(255)     | YES  |     | NULL    |       |
+| flags | int(10) unsigned | NO   |     | 0       |       |
 +-------+------------------+------+-----+---------+-------+
 				</programlisting>
 			</example>
@@ -209,7 +209,7 @@ iptel
 			attributes.</para>
 		</section>
 	</section>
-	
+
 	<section id="uid_domain.dep">
 		<title>Dependencies</title>
 		<para>
@@ -222,7 +222,7 @@ iptel
 	    </itemizedlist>
 		</para>
 	</section>
-	
+
 	<section id="uid_domain.known_limitations">
 		<title>Known Limitations</title>
 		<para>
@@ -231,7 +231,7 @@ iptel
 			reload will delete the original table still in use by the process.
 		</para>
 	</section>
-	
+
 	<xi:include href="params.xml"/>
 	<xi:include href="functions.xml"/>
 	<xi:include href="fifo.xml"/>