Trim trailing whitespace

Author: petk

.travis.yml

@@ -17,7 +17,7 @@ addons:
       - libxml2-dev
       - libcurl4-gnutls-dev
       - lcov
-      
+
 install:
   - gem install lcoveralls
 
@@ -43,7 +43,7 @@ env:
 before_script:
   # build the matrix' PHP version
   - make -f travis/pecl/Makefile php
-  # build the extension, the PECL variable expects the extension name 
+  # build the extension, the PECL variable expects the extension name
   # and optionally the soname and a specific version of the extension
   # separeated by double colon, e.g. PECL=myext:ext:1.7.5
   - make -f travis/pecl/Makefile ext PECL=solr
@@ -59,7 +59,7 @@ script:
 after_script:
   - lcov --no-checksum --directory . -f --capture --output-file coverage.info && lcov -f --remove coverage.info "/usr/*" -o coverage.info
   - lcoveralls -r .
-  
+
 notifications:
   email:
     - [email protected]

LICENSE

@@ -1,30 +1,30 @@
--------------------------------------------------------------------- 
+--------------------------------------------------------------------
                   The PHP License, version 3.01
 Copyright (c) 1999 - 2009 The PHP Group. All rights reserved.
--------------------------------------------------------------------- 
+--------------------------------------------------------------------
 
 Redistribution and use in source and binary forms, with or without
 modification, is permitted provided that the following conditions
 are met:
 
   1. Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
- 
+
   2. Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.
- 
+
   3. The name "PHP" must not be used to endorse or promote products
      derived from this software without prior written permission. For
      written permission, please contact [email protected].
-  
+
   4. Products derived from this software may not be called "PHP", nor
      may "PHP" appear in their name, without prior written permission
      from [email protected].  You may indicate that your software works in
      conjunction with PHP by saying "Foo for PHP" instead of calling
      it "PHP Foo" or "phpfoo"
- 
+
   5. The PHP Group may publish revised and/or new versions of the
      license from time to time. Each version will be given a
      distinguishing version number.
@@ -41,27 +41,27 @@ are met:
      "This product includes PHP software, freely available from
      <http://www.php.net/software/>".
 
-THIS SOFTWARE IS PROVIDED BY THE PHP DEVELOPMENT TEAM ``AS IS'' AND 
+THIS SOFTWARE IS PROVIDED BY THE PHP DEVELOPMENT TEAM ``AS IS'' AND
 ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A 
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
 PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE PHP
-DEVELOPMENT TEAM OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
+DEVELOPMENT TEAM OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 OF THE POSSIBILITY OF SUCH DAMAGE.
 
--------------------------------------------------------------------- 
+--------------------------------------------------------------------
 
 This software consists of voluntary contributions made by many
 individuals on behalf of the PHP Group.
 
 The PHP Group can be contacted via Email at [email protected].
 
-For more information on the PHP Group and the PHP project, 
+For more information on the PHP Group and the PHP project,
 please see <http://www.php.net>.
 
 PHP includes the Zend Engine, freely available at

README.ABOUT_SOLR_EXTENSION

@@ -1,7 +1,7 @@
 ================================================================================
 Introducing the Solr PHP Extension
 ================================================================================
-The Solr extension is an extremely fast, light-weight, feature-rich library that 
+The Solr extension is an extremely fast, light-weight, feature-rich library that
 allows PHP developers to communicate effectively with Solr server instances.
 
 There are tools to add documents and make updates to the solr server.
@@ -12,15 +12,15 @@ when searching for documents.
 There are also special objects that simplifies the sending of name-value requests
 to the server. This includes the SolrParams class and all its child classes.
 
-The SolrClient object allows one to communicate with Solr containers that are 
+The SolrClient object allows one to communicate with Solr containers that are
 behind proxy servers or that require HTTP Authentication to proceed.
 
 The SolrClient constructor accepts options such as
-http authentication username and passwor, proxy server name, port, login and 
+http authentication username and passwor, proxy server name, port, login and
 passwords etc.
 
 Using an advanced http client like libcurl allows us to leverage the features
-available with the library. We can reuse the HTTP connections without having 
+available with the library. We can reuse the HTTP connections without having
 to create a separate one for each request.
 
 ================================================================================
@@ -51,7 +51,7 @@ Each field is a SolrDocumentField object with the following public properties :
 
 Custom Serialization
 
-string SolrDocument::serialize(void) returns an XML document representing a 
+string SolrDocument::serialize(void) returns an XML document representing a
 SolrDocument as shown below :
 
 <?xml version="1.0" encoding="UTF-8"?>
@@ -107,16 +107,16 @@ C:12:"SolrDocument":679:{<?xml version="1.0" encoding="UTF-8"?>
 </solr_document>
 }
 
-One of the items on my todo list is to create a response writer to return 
+One of the items on my todo list is to create a response writer to return
 serialized SolrDocument objects instead of document arrays.
 
-SolrDocument::unserialize(string $serialized) accepts an XML document 
+SolrDocument::unserialize(string $serialized) accepts an XML document
 representing the SolrDocument object. It will the bring the object back to live.
 
-The SolrDocument class also has the method SolrDocument::getInputDocument() to 
+The SolrDocument class also has the method SolrDocument::getInputDocument() to
 allow one do get the SolrInputDocument version of a SolrDocument instance.
 
-This method may be helpful if one needs to resubmit the document to the server to 
+This method may be helpful if one needs to resubmit the document to the server to
 updates.
 
 The Solr extension has the SolrQuery object (a child of SolrParams) that enables
@@ -137,7 +137,7 @@ read-only SolrObject instances whose properties can also be accessed as array
 keys in addition to being accessible directly via the object->member notation.
 
 Having the properties accessible via object[member] notation is helpful in cases
-where the property name is not valid (contains dots and other characters not 
+where the property name is not valid (contains dots and other characters not
 legal in php.
 
 ================================================================================
@@ -146,7 +146,7 @@ How to Report Bugs
 
 Please report bugs to http://bugs.php.net
 
-If you experience a crash due to a segmentation fault, please follow the instructions on the link below 
+If you experience a crash due to a segmentation fault, please follow the instructions on the link below
 to get a gdb backtrace and then submit the trace in your bug report as well
 
 http://bugs.php.net/bugs-generating-backtrace.php

README.CONTRIBUTORS

@@ -29,13 +29,13 @@ Pierre-Alain Joye ([email protected])
  - Fine tuned and created the final version of the config.w32 script (291135)
  - Compiled and made available several versions of the .dll binaries for Windows.
  - Currently hosting the windows .dll binaries for the Apache Solr PECL extension.
- 
+
 ================================================================================
 Kalle Sommer Nielsen ([email protected])
 ================================================================================
  - Significant refactoring of the config.w32 script for Windows (288890)
  - Corrected Windows C++ compiler bugs (288890)
- 
+
 ================================================================================
 Pierrick Charron ([email protected])
 ================================================================================

README.INSTALLATION

@@ -78,19 +78,19 @@ This example assumes that the libxml2 and libcurl libraries were compiled from s
 
 and installed using "/root/custom/software" as the --prefix
 
-So the absolute path to the easy.h header file will be 
+So the absolute path to the easy.h header file will be
 
 /root/custom/software/include/curl/easy.h
 
-And the absolute path to the libxml/parser.h header file wil be 
+And the absolute path to the libxml/parser.h header file wil be
 
 /root/custom/software/include/libxml2/libxml/parser.h
 
 The absolute path to the xml2-config script will be /root/custom/software/bin/xml2-config
 
 And the absolute path to the curl-config script will be /root/custom/software/bin/curl-config
 
-Then you can pass libcurl prefix to the configure script for CURL and LIBXML respectively 
+Then you can pass libcurl prefix to the configure script for CURL and LIBXML respectively
 
 during the configuration phase as shown here :
 
@@ -99,7 +99,7 @@ during the configuration phase as shown here :
 If you already have the latest versions of the libraries then the step listed in 4A alone is sufficient.
 
 5. make && make install
- 
+
 This should compile the code and install it in the extension_dir specified in the ini file.
 
 Then open your php.ini file and add the following line to it
@@ -116,15 +116,15 @@ you will need to follow the following steps.
 
 This will build the Solr extension statically into php.
 
-After the installation is completed, you will have to restart your webserver for the changes to take effect. 
+After the installation is completed, you will have to restart your webserver for the changes to take effect.
 
 For CLI only use, you do not have to restart your webserver.
 
 ================================================================================
 On Windows
 ================================================================================
 
-If you are using a pre-compiled dll, simply copy the php_solr.dll file 
+If you are using a pre-compiled dll, simply copy the php_solr.dll file
 to your extension_dir specified in the ini file.
 
 Then open your php.ini file and add the following line to it
@@ -134,8 +134,8 @@ extension=php_solr.dll
 Then restart your webserver. For CLI only, you do not have to restart your webserver.
 
 If you are building from source, you will need to download the library dependencies
-for libxml and libcurl from the following link to the deps folder before 
-running buildconf.bat 
+for libxml and libcurl from the following link to the deps folder before
+running buildconf.bat
 
 http://wiki.php.net/internals/windows/libs
 
@@ -150,7 +150,7 @@ Windows DLLs are now available here
 http://downloads.php.net/pierre/
 
 If you are building from source, you will need to download the library dependencies
-for libxml and libcurl from the following link to the deps folder before 
+for libxml and libcurl from the following link to the deps folder before
 running buildconf.bat
 
 The Apache Solr extension can be compiled statically or shared.
@@ -181,7 +181,7 @@ cd c:\php-sdk\
 bin\phpsdk_setvars.bat
 bin\phpsdk_buildtree.bat php53dev
 
-7. Now extract the snapshot from Step 3 to C:\php-sdk\php53dev\vc9\x86 with your favourite unpacker so that the following directory gets created: 
+7. Now extract the snapshot from Step 3 to C:\php-sdk\php53dev\vc9\x86 with your favourite unpacker so that the following directory gets created:
 
 C:\php-sdk\php53dev\vc9\x86\php5.3-xyz
 
@@ -227,7 +227,7 @@ How to Report Bugs
 
 Please report bugs to [email protected]
 
-You can also register bugs here 
+You can also register bugs here
 
 http://pecl.php.net/bugs/report.php?package=solr
 

README.MEMORY_ALLOCATION

@@ -46,11 +46,11 @@ during the insert process.
 It will also call the destructor function if a valid one was passed when the
 HashTable was initialized with zend_hash_init().
 
-In the extension, I have used the p* version of the memory allocation functions 
+In the extension, I have used the p* version of the memory allocation functions
 to allow me toggle if there is any need to do so in the future. This will prevent
 a massive search and replace effort.
 
-For all the HashTables, I set the intial size to 8 to reduce the looping when 
+For all the HashTables, I set the intial size to 8 to reduce the looping when
 zend_hash_init() is setting up the HashTable pointer to use.
 
 

README.RELEASE_CHECKLIST

@@ -8,11 +8,11 @@ svn co http://svn.php.net/repository/pecl/solr/trunk pecl-solr
 
 cd pecl-solr
 
-phpize 
+phpize
 
 ./configure
 
-make 
+make
 
 make install
 

README.SUBMITTING_CONTRIBUTIONS

@@ -9,9 +9,9 @@ experience very minimal defects during usage.
 
 New ideas, corrections, bug fixes, feature improvements are always welcome.
 
-However, you must discuss any changes you are about to make to any of 
+However, you must discuss any changes you are about to make to any of
 the source files prior to making or submitting such changes either in the
-PECL developers mailing list ([email protected]) or by contacting the 
+PECL developers mailing list ([email protected]) or by contacting the
 current author(s) or maintainer(s) of this extension directly.
 
 Test scripts should be included when making the submissions.
@@ -45,7 +45,7 @@ Checklist for making submissions
    web server error logs when you test your patch?
  - Did you build PHP for multi-threaded web servers.
  - Did you create test script for "make test"? (Recommended)
- - Did you check your patch is unified format and it does not 
+ - Did you check your patch is unified format and it does not
    contain white space changes?
  - Did you read the patch again?
- 
+

README.md

@@ -35,8 +35,8 @@ Please make sure to install them before proceeding to the compilation process
     make
     make test
     sudo make install
-``` 
-  
+```
+
 more details on README.INSTALLATION
 
 Contributions
@@ -67,7 +67,7 @@ How to Report Bugs
 
 Please report bugs to http://bugs.php.net
 
-If you experience a crash due to a segmentation fault, please follow the instructions on the link below 
+If you experience a crash due to a segmentation fault, please follow the instructions on the link below
 to get a gdb backtrace and then submit the trace in your bug report as well
 
 http://bugs.php.net/bugs-generating-backtrace.php

TODO

@@ -5,10 +5,10 @@
 Features and things to do in the library
 ================================================================================
 
-- Set up php.ini entries for default servlet values. 
-  
+- Set up php.ini entries for default servlet values.
+
   This will allow developers to set custom values for the servlets.
-  
+
 - Ability to send custom requests to Solr (custom url, custom request contents)
 
 - Ability to add files (pdf, office documents, etc)