[Erp5-report] r14054 - /erp5/trunk/utils/oood/README

[nobody at svn.erp5.org]

Author: bartek
Date: Wed Apr 11 18:45:03 2007
New Revision: 14054

URL: http://svn.erp5.org?rev=14054&view=rev
Log:
some notes about upcoming new implementation

Modified:
    erp5/trunk/utils/oood/README

Modified: erp5/trunk/utils/oood/README
URL: http://svn.erp5.org/erp5/trunk/utils/oood/README?rev=14054&r1=14053&r2=14054&view=diff
==============================================================================
--- erp5/trunk/utils/oood/README (original)
+++ erp5/trunk/utils/oood/README Wed Apr 11 18:45:03 2007
@@ -1,3 +1,17 @@
+NEWS
+
+The request handling part is going to be rewritten completely - the
+serw. Procesor class will be replaced by Dispatcher, which will be the
+only handler for timeouts and exceptions.
+
+The rewrite started on April 11, and will take a week, hopefully, or
+more if it goes wrong. Once it reaches an alpha state, there will be a
+commandline switch so that you can use the old implementation or the new
+one.
+
+For now, Dispatcher is almost pseudo-code. Pool contains some
+placeholders for the new implementation.
+
 DESCRIPTION
 
 A server for converting docs from other formats to OOo, generating pdf
@@ -12,15 +26,16 @@
     2.0.3-7
     2.1.0-6
 
-A combination of Python 2.5 and OpenOffice 2.1 does NOT work because of incompatibility of pyuno.
+A combination of Python 2.5 and OpenOffice 2.1 does NOT work because of
+incompatibility of pyuno.
 
 INSTALLATION:
 
 Refer to http://wiki.erp5.org/HowToUseOood for most up-to-date
 instruction about setting up the environment and installing oood.
 
-If you install from source, remember to create a writable tmp directory under
-your oood base dir.
+If you install from source, remember to create a writable tmp directory
+under your oood base dir.
 
 SETUP:
 
@@ -32,9 +47,15 @@
 
 - pool_size - how many OpenOffice instances you want to start
 
-- instance_load_time - how long it takes for your machine to load an OOo instance; this is important because when it is restarted, a script spawns a new instance and then has to wait before trying to connect, and also because if another instance is started too soon (before the previous one loads completely) they are both merged into one.
+- instance_load_time - how long it takes for your machine to load an OOo
+  instance; this is important because when it is restarted, a script
+  spawns a new instance and then has to wait before trying to connect,
+  and also because if another instance is started too soon (before the
+  previous one loads completely) they are both merged into one.
 
-- instance_timeout - when an OOo instance we called does not return for too long, we decide it has crashed; we kill it and start another one. This is the time after which we undertake this drastic action.
+- instance_timeout - when an OOo instance we called does not return for
+  too long, we decide it has crashed; we kill it and start another one.
+  This is the time after which we undertake this drastic action.