On Wednesday, November 6, 2013 2:25:56 AM UTC-5, raimonesteve wrote: > > Hello, > > If you select Django and Tryton, you need a connector because database > o models are different > > 1- Add webservices in Django, for example, Tastypie. And a module in > Tryton call this webservices. > 2- If Django is in same server than Trytond, in your django view code > you could import trytond. For me the best option. > 3- You could import proteus in Django (could you run Django is not > same server than Trytoind), but some moths ago, I read is low proteus > when work with big data. Anybody could confirm this? >
Cedric confirmed in an August thread that proteus wasn't designed for speed. Where proteus should really shine is in high level testing where it can easily simulate a client. > 4- Migrate a Nereid. 100% integrated a Trytond. > Even though the Nereid guys have done awesome work I don't consider that Nereid's integration with the latest versions of Tryton is really on par to be considered production ready. We had problems getting to run nereid-project with Tryton 2.8. I saw some pull requests to update nereid to 3.0 (I think it was you Raimon who opened them) but they aren't quite ready. Perhaps someone really interested in leveraging all the good work Sharoon and the Openlabs team has done should release some updated and comprehensive docs on getting it to run correctly. Right now it seems that among the options you've mentioned either 1 or 2 are the best ways to integrate Django and Tryton. Probably 2 is the better option in terms of both performance and easiness of getting it up and going. -- Breno
