diff options
| author | Xavier Morel <xmo@openerp.com> | 2011-12-19 15:57:59 +0100 |
|---|---|---|
| committer | Xavier Morel <xmo@openerp.com> | 2011-12-19 15:57:59 +0100 |
| commit | 75409e349a0ca4488e477b9621991145e6890d5c (patch) | |
| tree | a59abad97fc856f761e50cfd5b39b82cacffe111 /addons/analytic_user_function/analytic_user_function_view.xml | |
| parent | 248654d97e88a9e45506791a738be1ae3e801df3 (diff) | |
[FIX] avoid systematically deadlocking the stand-alone OpenERP web in its default configuration
The default configuration for OpenERP Web standalone (launched via the
openerp-web script) is single-threaded for log-readability purposes.
web.common.controllers.main.Proxy.load has been added to wrap a
request to an HTTP handler inside a JSON (and/or JSONP) request, the
initial implementation was to perform a full HTTP call *from within an
HTTP handler to itself*.
Since the server is single-threaded and its only thread is already
busy, it can't handle the new request, and the client deadlocks.
Replaced this crap by also-crap-but-slightly-less-so: instantiating a
Werkzeug test client using the root application and proxying the
request through that. Avoids creating a new request from the server,
therefore does not deadlock.
lp bug: https://launchpad.net/bugs/905384 fixed
bzr revid: xmo@openerp.com-20111219145759-m10zgo3tcd6zjhcu
Diffstat (limited to 'addons/analytic_user_function/analytic_user_function_view.xml')
0 files changed, 0 insertions, 0 deletions
