[bop-devel] Python gateway module

[Jo Rhett]

On Aug 25, 2006, at 12:42 PM, Ivan Kohler wrote:
> FWIW, I don't have any if/the/else logic for different payment  
> gateways
> in my use of B:OP.  You may want to get involved more and at least let
> us know the specific differences that you're running into here.

The very obvious case.  The variables you need to supply change  
depending on the payment vendor.

In our local payment api, the variables are unified completely.  The  
only if/then/else stuff is within the payment module.

> A better job in what way, specifically?  As I said, my application
> doesn't have any idea about the destination API, and I've used it with
> dozens of gateways.  If your specific usage isn't finding things
> sufficiently abstracted by B:OP, it would be great if you could  
> tell us
> specifically what problem with that you're running into with that  
> rather
> than speak about it only general terms.
	....
> A new major version and API change seem to be a common request, but  
> I'm
> having trouble understanding what we gain by this.  Why do the
> invocation methods have to all change?  I would really prefer to  
> support
> new functionality in a backwards-compatible fashion.

Valid complaint.  I'll update the test environment to the very latest  
code and provide examples sometime in the first week of September.   
(I'm on vacation at the moment, and next week will be a short week  
spent getting caught up)

-- 
Jo Rhett @ Lizard Arts
velociRaptor Racing #563