trytond as a Django database backend (or should we just use Flask)

[M. Murray]

Here's my dilemma. I have two use cases, both of which require  web application to be constructed and we would like to standardise on a single framework for web application design/development. 

We're already using Tryton and GNU Health - now we want to create some, initially simple, web-apps that will read and write data to trytond. The choice is between Django and Flask.

Use case 1: Web app runs in the public talking to trytond in a private network over XMLRPC or JSONRPC

In this case, Django and Flask on equal footing in terms of tryton integration - we need a client library.

Use case 2: Web app runs in the same server as trytond, accessible to people who also have tryton logins - flask-tryton gives flask an advantage here.

However, we feel that Flask is less nice than Django for building web-apps whose requirements are not fully known in the beginning.

For this reason, we have decided to build a custom Django Database Backend that uses trytond as it's database. It would work in two different ways, depending on the backend-class that you select. One backend class would talk to a remote trytond over jsonrpc and the other would talk to a local trytond by importing stuff from trytond.* (similar to how flask-tryton works).

Comments, warnings and suggestions please.

---

MM

[Cédric Krier]

On 2016-07-11 13:09, M. Murray wrote:
> Comments, warnings and suggestions please.

A better place would be http://groups-contrib.tryton.org/

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/