From acd87065264891c615932739a86d5c8c1213f13d Mon Sep 17 00:00:00 2001 From: Vincent Pelletier <vincent@nexedi.com> Date: Wed, 27 May 2009 15:59:19 +0000 Subject: [PATCH] Caching cannot and must not be done at this level, because it can be desired to get different connections. As an example, in MySQL transaction information is local to a connection. So returning an existing connection is not always the same as creating a new one, and only the class doing the actual connection knows what can be shared and what cannot. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27219 20353a03-c40f-0410-a6d1-a30d3c3de9de --- product/ERP5Type/Tool/WebServiceTool.py | 1 - 1 file changed, 1 deletion(-) diff --git a/product/ERP5Type/Tool/WebServiceTool.py b/product/ERP5Type/Tool/WebServiceTool.py index 5ef5842aeb..665a870590 100644 --- a/product/ERP5Type/Tool/WebServiceTool.py +++ b/product/ERP5Type/Tool/WebServiceTool.py @@ -87,7 +87,6 @@ class WebServiceTool(BaseTool): of any kind of web service (not only ERP5) with many different kinds of transport like 'xml-rpc' or 'soap' """ - # XXX: implement connection caching per zope thread if transport_kw is None: transport_kw = {} connection_handler_klass = connection_plugin_registry[transport] -- 2.30.9