Luckily there were tons of improvements in OpenERP 5 vs 4.2 so even if
concurrency is not yet possible without starting several instances,
server requests are often faster so you don't feel latency to often.
I see what you're saying and your test is quite clear but can you give
> your take on the following comment from Raphaël ?
> Is he referring to specific portions of the app?
No, I think he is simply wrong. The whole server is multi-threaded,
multi-users and manages concurrencies efficiently/transactional. (since
v3, I think). The server does one thread per rpc request and, some
specific operations may launch others threads: procurement computation,
reports.
Some parts of the GTK client are multi-threaded (checking if they are
attachments or requests) and others are not: when you print a report.
That could be the reason why some may think it's not multi-threaded.
But it's on the GTK client, the server is fully multi-threaded and
manages easily hundreds of users at the same time. It has no effect on
concurrencies or multi-threads or simultaneous users.
--
Fabien Pinckaers
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users
