[bop-devel] inconsistencies / a need for a more formal B::OP
specification?
Jo Rhett
jrhett at netconsonance.com
Thu Dec 7 02:28:48 PST 2006
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'});
...etc
We don't get into if/then/else code until farther down, so being able to
avoid using processor options provides us with a lot more flexibility.
--
Jo Rhett
Network/Software Engineer
Net Consonance
More information about the bop-devel
mailing list