[bop-devel] inconsistencies / a need for a more formal B::OP specification?

[Ivan Kohler]

On Thu, Dec 07, 2006 at 02:28:48AM -0800, Jo Rhett wrote:
> Jo Rhett wrote:
> >For various reasons it is really tough for our 
> >application to have %processor options.  It would be ideal for me if you 
> >could set all of the processor options later by method:
> >
> >$tx->processor_opt(1);
> >$tx->processor_opt(2);
> >...etc.
> 
> To clarify what I meant, our main purchase module has this code:
> 
> # Get the appropriate modules
> eval "use Business::OnlinePayment";
> &processingError( $@ ) if $@;
> eval "use Business::OnlinePayment::$CONFIG->{'Auth_Service'}";
> &processingError( $@ ) if $@;
> my $transactor = new Business::OnlinePayment($CONFIG->{'Auth_Service'});

Just for comparison, my app does something not unlike:

my $transactor = new Business::OnlinePayment( $CONFIG->{'Auth_Service'}, 
                                              $CONFIG->{'Auth_Options'} 
                                            );

and allows setting of the key/value pairs in the config UI.

Having a standard way for processor modules to declare their auth 
options (and having a way to ask them what they are, maybe even for 
descriptions) is looking like a better and better idea...  A 
configuration UI could then use this for processor setup...

-- 
_ivan