Thanks a lot for your reply, after some investigation, we came to the same conclusion :)
We like the second option you propose: Fedicom Client and OpenERP module with the SocketServer library. Problems: a) Not too much info of the Fedicom protocol. The most valuable, this old one from a software developer: http://www.rentasoft.es/compufarma/_docu/pa001332.htm Not sure if this have changed recently. b) The message recieved through the Fedicom client is a new sale order. But it's not directly created in OpenERP (I wish!), it's necessary to make first a stock check in OpenERP, and then: - return an ok message (easiest case, we have everything in stock) - return a completely not ok message (easy case also, we have nothing in stock) - return a not ok message (we have some quantity of some items in stock, list them, and wait for the possible of the client in them) In the third case (and maybe in first?), we wait for the new answer of the client, and during that time, the stock of that items has to be always enough to satisfy the client demands. I mean, this has to generate some kind of item and quantity reservation, while the client decides if is interested or not. We'll continue posting our findings. Again, thanks a lot for your post! ------------------------ Carlos Liébana Anero www.ting.es -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=59886#59886 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
