On Fri, Sep 19, 2008 at 1:27 AM, Bojan Mihelac <[EMAIL PROTECTED]> wrote:
> > Thanks again for clarification Bruce. > In my case gateway redirect user to SUCCESS or FAILURE page. I both > cases shop shuld validate signature and that is the reason for not > using payment.common.views.checkout view to clear shopping cart. > Those changes to the payment system plumbing are now in the trunk code. They should make it *much* easier for custom payment gateway creators. I did it because I was implementing/integrating Prot/X. That gateway needs an extra step, "secure3d", which was not really possible to do using the previous plumbing. That, and when I started looking at it again, it took me a couple hours to figure out how the code worked, even though I wrote much of it. Ouch. That's not a good recipe for maintainable, testable development. So, I refactored it and made it much more object-oriented, in a backwards-compatible way. Now all the payment gateways use a "simple" PaymentController object which maintains state without ten thousand parameter calls. Much more understandable. +Bruce Kroeze http://gosatchmo.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
