Contributors mailing list archives
Re: Request for new project oca/queueby
Leonardo Rochael Almeida
An enthusiastic +1 from me!
There are many nice enhancements that could be added to the queue project, including adding dependencies between tasks and things like:
* Do all tasks like Y in parallel, then, after they are done, do all tasks like X in parallel.
These kinds of improvements can be made completely backward compatible with the current queue architecture, but would allow much faster speed and better hardware use for heavy operations (think Pull/Push replenishment rules, which are currently done in background, but on a single hardly monitored thread that is launched manually).
On 10 October 2016 at 09:38, Guewen Baconnier <email@example.com> wrote:
Hi, This is an important step in the evolution of the connector framework. The job queue has proved to be versatile and has been used in many more uses that mere connectors. Therefore, I took a step forward and during the code sprint last week, I started to split the connector addon in two: * queue_job: extraction of the job queue (with a great rework BTW) * connector: the remaining stuff for developing connectors (backends, ConnectorUnit classes, ...) This is targeted for Odoo 10. To gain broader interest, I want to "unbrand" the job queue from the "connector" naming. I propose a new OCA project which would be "oca/queue". The PSC would be, at least at the beginning, the same than the OCA/connector one for simplicity. Does it sound good to you? -- Guewen Baconnier Business Solutions Software Developer Camptocamp SA PSE A, CH-1015 Lausanne Phone: +41 21 619 10 39 Office: +41 21 619 10 10 http://www.camptocamp.com/