From 132454d6d12a48252bf83ff7efc9555475176044 Mon Sep 17 00:00:00 2001 From: Stefan Sayer Date: Thu, 25 Sep 2008 23:06:13 +0000 Subject: [PATCH] added MT note git-svn-id: http://svn.berlios.de/svnroot/repos/sems/trunk@1108 8eb893ce-cfd4-0310-b710-fb5ebe64c474 --- doc/Readme.xmlrpc2di | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/doc/Readme.xmlrpc2di b/doc/Readme.xmlrpc2di index 4c7105f0..ab5d087e 100644 --- a/doc/Readme.xmlrpc2di +++ b/doc/Readme.xmlrpc2di @@ -22,8 +22,16 @@ A small patch set needs to be applied as well: patch -p0 < xmlrpcpp07_sems.patch If xmlrpcpp is extracted to a different directory, the path in -the Makefile needs to be adapted. +the Makefile needs to be adapted. If your xmlrpc++ installation has the +SSL for xmlrpc client option, you may need to add -DHAVE_XMLRPCPP_SSL +to module_cflags due to some ambiguity in the header. +The XMLRPC server can be configured to run as single threaded server (if +one request is executed, the next ones have to wait), or a multi-threaded server +with a thread pool, in which case the callers only have to wait if there are +as many requests served in parallel as threads. Note that it is a good idea to +implement DI functions thread-safe, as they may be called from different threads +in SEMS anyway. Configuration parameters ------------------------ @@ -41,6 +49,10 @@ Configuration parameters server_retry_after 10 retry a failed server after n seconds + multithreaded yes MT or default server + + threads 5 only in case of multithreaded + Using XMLRPC2DI client over DI ------------------------------