Re: Please review control and templates for tryton-server

* Mathias Behrle: " Re: Please review control and templates for tryton-server"
  (Wed, 14 Sep 2022 21:22:47 +0200):

> * Justin B Rye: " Re: Please review control and templates for tryton-server"
>   (Wed, 14 Sep 2022 14:21:44 +0100):


> I will merge the changes and propose the final results to you.

I merged your changes almost completely unchanged, please have a look at

> > >>> Template: tryton-server-postgresql/db-admin-email    
> > [...]  
> > >>> Template: tryton-server-uwsgi/enable-workers    
> > [...]  
> > >     
> > >>>  If workers are configured those tasks (like e.g. the processing of
> > >>> sales, invoices or purchases) can be automatically performed by
> > >>> workers. They do not wait for completion in the clients thus removing
> > >>> the need of waiting and doing serialized steps.      
> > >> 
> > >> Well, obviously not waiting eliminates some waiting, but it's not
> > >> quite clear what's going on with the serialised steps... maybe:
> > >>
> > >>    If enabled, the workers can automatically perform tasks such as the
> > >>    processing of sales, invoices, or purchases without waiting for the
> > >>    clients to finish, thus removing the need for serialisation.    
> > > 
> > > The serialized steps are mostly workflow steps that when called manually
> > > take some time to complete. Pushing those tasks to a worker doesn't block
> > > the client until the process has finished but allows to continue almost
> > > immediately. The serialized process is just handled by another process.
> > >  
> > 
> > All in all I think it's clearer if it just stops at "without waiting
> > for the clients to finish".  For a start it hides the fact that I
> > mis-localised "serialisation".  

+ If enabled, the workers can automatically perform tasks such as the
+ processing of sales, invoices, or purchases removing the need to execute
+ particular workflow steps manually in the clients and wait for them
+ to finish.

Is that understandable?




-- 

    Mathias Behrle
    PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
    AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6