On Friday, May 15, 2015 at 4:35:03 AM UTC-5, Cédric Krier wrote: > > On 15 May 02:22, raimonesteve wrote: > > > > > > El dissabte, 22 novembre de 2014 22:58:37 UTC+1, M. Murray va escriure: > > > > > > I have been reading and learning a lot about Tryton. One thing I have > > > noticed is that the trytond communicates with the client using what is > > > essentially HTTP. Correct me if I'm wrong please. > > > > > > The point of this post is to ask the following questions: > > > > > > > > > 1. As far as I know, the default Python (from python.org) doesn't > > > support multiple cpu cores. Therefore, even though trytond uses 1 > thread > > > per user, a single trytond instance will only use a single CPU > core. > > > Correct? > > > 2. Does Trytond communicate with the tryton client using the HTTP? > > > 3. Has anyone deployed trytond in production behind HTTP or other > > > proxy? > > > > > > > > > In my experiments, I have modified trytond to accept two new options > on > > > the command line, --jsonrpc-port (-j) and --xmlrpc-port (-x). I then > use > > > the following script to start 3 instances. The same effect can be > achieved > > > with 3 different config files. > > > > > > > IMHO it's not necessary modify trytond because you could clone > trytond.conf > > file; and each cfg file add json/xml/webdav port (in your example, 9297 > > 9298 9299 > > > > An idea to not clone some sections in cfg is an include but I think is > not > > possible include some sections from other cfgs (I'm not sure) > > One thing, I would like is to allow to define many configuration files > that will update each one in command line order. So like that you can > share a common configuration and extend it with custom one. > > So this would be like executing :
trytond -c base_cfg.conf -c mytrytond.conf The second file (mytrytond.conf) could contain only the values that make the configuration different from the base_cfg. If that's what you mean, I quite like it. -- MM
