Thanks Guewen for your explanations and tricks. I'm glad to finally know of that return value thing. A further fix is under way.
Yes, each handler is called for each bank. Normally, it's not a problem because each handler handle the payment they are able to handle and once that happen, the handler is supposed to flag the payment request as "sent" (only payment in "waiting" mode are sent to handlers). So double charging isn't supposed to happen. Of course, if a handler misbehave and doesn't correctly set the payment request's state to "sent", then it can happen, but it would be a bug in the handler. As for the possible import bug, yeah, I saw in C2C's new connector framework's comments that such thing can happen, but I'm not sure that the possibility of that happening is enough to warrant a complexification of the import mechanism. Do you think that this possibility is a deal breaker? -- https://code.launchpad.net/~savoirfairelinux-openerp/banking-addons/loose-coupling/+merge/185033 Your team Savoir-faire Linux' OpenERP is subscribed to branch lp:~savoirfairelinux-openerp/banking-addons/loose-coupling. -- Mailing list: https://launchpad.net/~savoirfairelinux-openerp Post to : [email protected] Unsubscribe : https://launchpad.net/~savoirfairelinux-openerp More help : https://help.launchpad.net/ListHelp
