Remove BufferingHTTPServer, reuse the header parser of BaseHTTPServer

README

@@ -79,8 +79,8 @@ OPTIONAL
 --------
 
 - MySQLdb (http://sourceforge.net/projects/mysql-python)
-	- Mysql server 4.0+ for Mysql authentication with
-	  with read/write access to one database
+- Mysql server 4.0+ for Mysql authentication with
+  with read/write access to one database
 
 
 NOTES

doc/ARCHITECTURE

@@ -4,28 +4,18 @@ OVERVIEW
 
 Here is a little overview of the package:
 
-A. In the DAV/ package:
+A. In the pywebdav/lib/ package:
 
-    1. BufferingHTTPServer
-
-       This is the same as the normal BasicHTTPServer but instead of
-       directly sending each string over the network this implementation
-       caches it and sends it at once after finishing one request.
-
-       This has the advantage that clients like cadaver don't break as
-       they want to peek at the next lines when encountering e.g. a header.
-
-    2. AuthHTTPServer
-
+    1. AuthHTTPServer
        This works on top of either the BasicHTTPServer or the 
        BufferingHTTPServer and implements basic authentication.
 
-    3. WebDAVServer
+    2. WebDAVServer
        This server uses AuthHTTPServer for the base functionality. It also uses
        a dav interface class for interfacing with the actual data storage (e.g.
        a filesystem or a database).
 
-B. In the PyDAVServer directory:
+B. In the pywebdav/server/ directory:
 
     1. server.py
        Main file for server. Serves as a start point for the WebDAV server
@@ -47,59 +37,21 @@ B. In the PyDAVServer directory:
        PyWebDav configuration file.
 
 
-Class Tree
-----------
-
-PyWebDAVServer.fileauth.DAVAuthHandler
-<Very simple handler for authentication. Must have its data
-injected (look at server.py). Overwrites get_userinfo from AuthRequestHandler>
-
-            |
-            |
-            |
-
-DAV.WebDAVServer.DAVRequestHandler
-<Provides methods for DAV commands. These methods are triggered
-by AuthRequestHandler.handle().>
-
-            |
-            |
-            |
-
-DAV.AuthServer.BufferedAuthRequestHandler
-<Calls the right methods to buffer request data>
-
-        |                      |
-        |                      |
-        |                      |
-
-DAV.BufferingHTTPServer     DAV.AuthServer.AuthRequestHandler
-<Saves the complete result  <Overwrites handle() method in order
-in one file and returns     to provide authentication and to pass
-only if request is          control to the do_ methods handling
-complete>                   DAV commands>
-
-
 Information
 ----------
 
 This document describes the architecture of the python davserver.
 
-The main programm is stored in DAV/WebDAVServer.py. It exports a class WebDAVServer
-which is subclassed from AuthServer which again is subclassed from 
-BufferingHTTPServer.
-
-The BufferingHTTPServer class extends the BaseHTTPServer class by
-storing all output in a buffer and sending it at once when the request
-is finished. Otherwise clients like cadaver might break.
+The main programm is stored in pywebdav/lib/WebDAVServer.py. It exports a class
+WebDAVServer which is subclassed from AuthServer.
 
 The AuthServer class implements Basic Authentication in order to make
 connections somewhat more secure.
 
 For processing requests the WebDAVServer class needs some connection to
 the actual data on server. In contrast to a normal web server this
 data must not simply be stored on a filesystem but can also live in
-databases and the like.  
+databases and the like.
 
 Thus the WebDAVServer class needs an interface
 to this data which is implemented via an interface class (in our
@@ -124,10 +76,9 @@ following:
   You might use the existing class as skeleton and explanation of which 
   methods are needed.
 
-That should be basically all you need to do. Have a look at PyDAVServer/fileauth.py in order
-to get an example how to subclass WebDAVServer.
+That should be basically all you need to do. Have a look at
+pywebdav/server/fileauth.py in order to get an example how to subclass
+WebDAVServer.
 
 ===
 * describe the methods which need to be implemented.
-
-

doc/Changes

@@ -1,11 +1,14 @@
 
-0.9.8 (Feb 2011)
-----------------
+0.9.8
+-----
 
 Restructured. Moved DAV package to pywebdav.lib. All integrators must simply replace
 ''from DAV'' imports to ''from pywebdav.lib''.
 [Simon Pamies]
 
+Remove BufferingHTTPServer, reuse the header parser of BaseHTTPServer.
+[Cédric Krier]
+
 Fix issue 44: Incomplete PROPFIND response
 [Sascha Silbe]
 

doc/TODO

@@ -2,10 +2,10 @@ GENERAL
 -------
 
 - web page needs to get done:
-	- Download
-	- News
-	- TODO list
-	- Changes
+    - Download
+    - News
+    - TODO list
+    - Changes
     - Name
 
 - use a better solution than DAV/INI_Parse.py [Stephane Klein]

doc/interface_class

@@ -15,7 +15,7 @@ and change it. You actually have implement the following methods:
 
 
 
-get_childs(self,uri)
+get_childs(self, uri, filter=None)
 
     This method should return a list of all childs for the
     object specified by the given uri.
@@ -29,10 +29,10 @@ get_props(self,uri,values=None,all=None,proplist=[])
     about properties for the object specified with the given uri.
     The parameters are as follows:
 
-    values	-- ?? cannot remember ;-)
-    all		-- if set to 1 return all properties
-    proplist	-- alternatively you can give get a list of
-		   properties to return 
+    values      -- ?? cannot remember ;-)
+    all         -- if set to 1 return all properties
+    proplist    -- alternatively you can give get a list of
+                   properties to return
 
     The result of this method should be a dictionary of the form
 
@@ -50,15 +50,15 @@ get_data(self,uri)
 
 
 get_dav(self,uri,propname)
-    
+
     This method will be called when the server needs access to a DAV
     property. In the example implementation it will simply delegate it
     to the corresponding _get_dav_<propname> method. You maybe should
     handle it the same way.
 
 
 _get_dav_<propname>(uri)
-    
+
     These methods will be called by get_dav() when the value of a DAV
     property is needed. The defined properties are:
 
@@ -100,7 +100,7 @@ rmcol(self,uri)
 
 
 rm(self,uri)
-    
+
     This is the same for single objects, the same as above applies.
 
 

doc/walker

@@ -3,7 +3,7 @@ Walker methods
 
 In the COPY, DELETE and MOVE methods we need to walk over
 a tree of resources and collections in order to copy, delete
-or move them. 
+or move them.
 
 The difference between all these walks is only that we perform
 a different action on the resources we visit. Thus it might be
@@ -28,17 +28,17 @@ perform on it.
 
 
 Here the iterative approach (in order to save memory):
-dc=dataclass
-queue=list=[start_uri]
+dc = dataclass
+queue = list = [start_uri]
 while len(queue):
-    element=queue[-1]
-    childs=dc.get_childs(element)
+    element = queue[-1]
+    childs = dc.get_childs(element)
     if childs:
-	list=list+childs
+        list = list + childs
     # update queue
-    del queue[-1]   
+    del queue[-1]
     if childs:
-	queue=queue+childs
+        queue = queue + childs
 
 
 (first try..)