IRC logs of #tryton for Tuesday, 2012-09-18 #tryton log beginning Tue Sep 18 00:00:02 CEST 2012
-!- tflorac(5bcfb0c6@gateway/web/freenode/ip. has left #tryton11:43
-!- vegai(~vegai@archlinux/developer/vegai) has left #tryton13:31
adeb6600is there a defined way for event management in tryton? im looking at multiple access to trytond from different location how does trytond sycronises all these events18:03
nicoeadeb6600: I don't understand18:05
nicoeadeb6600: What ar you trying to do18:05
juanfeadeb6600 I know that trytond can manage it as a transaction, see in
adeb6600nicoe: consider me a newbie my line of thought is trytond responds to json-rpc calls from the client. my question is more like can trytond update multiple clients of the changes made by one client?18:25
cedkadeb6600: please provide a usecase18:25
bechameladeb6600: the server works like a web-server, it does not push info to the client.18:28
adeb6600bechamel: that answers my question if trytond does not push information to client then it cannot update multiple clients of updates/changes made by one client18:32
cedkadeb6600: we use a optimistic locking system to prevent conflict18:36
cedkadeb6600: it is enough for most of the usage18:36
cedkadeb6600: what is yours?18:36
adeb6600Cedk: im considering tryton as the platform for an hotel management system network covering over 1000 small hotels ... thats my scenario18:44
cedkadeb6600: and where do you need pushing?18:45
bechameladeb6600: and you want to inform users when a room has been reserved ?18:45
adeb6600Yes much more there is a central organisation that effectively pushes data to each of these organisations18:47
adeb6600cedk: a monitoring organisation pushes data to each of these hotels18:48
bechameladeb6600: and each kind of info needs to be pushed in realtime ?18:49
cedkadeb6600: don't understand, Tryton is one database central18:49
bechameladeb6600: sorry, I made a typo, my question was: _which_ kind of info need to be pushed ?18:52
adeb6600cedk: yes i know tryton is one database central. a better scenario will using tryton as the backend erp of an online store with the need for purchase request on the web store to be pushed realtime to the backend18:53
bechameladeb6600: but maybe you are talking about a federation of server: each hotel as one server whith his own data, and then there is a central sever that provide data that must be synced with the hotel servers18:54
cedkadeb6600: so has to be pushed?18:55
bechameladeb6600: this is a common scenario, if the frontend call the tryton sever, it's a standart client-server behaviour18:56
adeb6600bechamel : exactly thats the perfect scenario18:56
cedkso no question :-)18:59
adeb6600bechamel:the frontend does not call the central server19:03
adeb6600bechamel: at least not directly19:04
cedkadeb6600: why?19:09
adeb6600cedk: because the central server(entity) is not an hotel it is a monitoring entity19:12
cedkadeb6600: and why this is preventing to connect to it?19:14
katrcedk: Hi!19:26
cedkkatr: hi19:27
katrcedk: Regarding your comment about account_dunning: When I started writing the module I did not consider releasing it to the public. But as dunning is something really common, I thought maybe it would be useful for someone else.19:27
katrThe usecase is quite simple: A customer does not pay an overdue receivable entry.19:28
cedkkatr: yes I understand the use case, but it is about how to solve it19:28
katrYou have to remind him to do so. Further more (but this would go to some other module in the future maybe), you will remind him and charge dunning fees.19:29
katrcedk: The code is only 300 SLOC and contains a lot of boiler plate stuff, so I'm open to any discussion.19:30
katrI'm not yet in production use with that module.19:31
cedkkatr: first step is to agree on a design19:33
cedkkatr: if you want to have such agreement, you have to provide a blueprint about it19:33
katrcedk: Sorry, I'll have to leave for a moment. Will be back later.19:35
cedkkatr: also I'm particulary concern about it because you said you took it from OpenERP19:35
cedkalso I think it is not a so easy task as it could look19:36
katrcedk: Just to get the record straight: I did not copy one single line from Open ERP.21:08
katrcedk: Basically I only see two possible ways to implement this: Add something to the move line or have a separate object. Because of simplicity I have chosen the first version, which coincide with the way they have done it.21:09
katrcedk: The blueprint should be similar to the blueprints in the wiki I suppose?21:13
katrcedk: How can I publish it?21:14
katrcedk: Are there any particular difficulties your are foreseeing?21:21
cedkkatr: I can give you access to wiki, just send me your google account22:25
cedkkatr: I don't like to mix accounting information with document information22:25
katrcedk: kantntreiber@gmail.com22:26
katrcedk: With document information you mean the dunning process?22:27
cedkkatr: yes it is just information about document22:28
katrcedk: I don't like it either. It was just the easiest way to achieve what I want.22:31
cedkkatr: for me, such design will exclude inclusion in Tryton22:32
cedkkatr: you have acces to wiki22:33
cedkkatr: the rules are: don't duplicate, use links, keep the structure, put comment for any changes22:33
katrkatr: As I already said, we can discuss and change the design. The push to the code review was just to get things rolling.22:34
katrcedk: O.K.22:34
cedkkatr: my goal is to use a methodology to design modules for Tryton22:44
katrcedk: It's a good thing, to have some kind of PEP-like process in Tryton. I just didn't know that it's necessary for something small like the dunning module.22:48
cedkkatr: I think it is not small22:49
cedkkatr: I have to think more about it but I see that we could make something better22:50
katrcedk: But even with something small, it makes sense that someone not following or the IRC channel to point out some issues.22:50
cedkkatr: but right now, I'm busy with the AR patch22:50
katrkatr: AR: I know, it's a lot of work. But I'm really looking forward for the next release.22:51

Generated by 2.11.0 by Marius Gedminas - find it at!