Re: New hierarchy for payment processors?

> On Sun, 23 Jul 2000, Sterling Hughes wrote: > > > PEAR is a part of PHP (currently), therefore it is automatically installed > > along the the rest of PHP. Sort of like Perl comes with a standard module > > set. > > Understood... Does it automatically put the install location in the > include path? I can't see any documentation on how to use it, presumably > it is in early stages? > Yes, its in its early stages. As of CVS and 4.0.2 the include_path is set automatically (I think). > > > > hierarchy needs to be established. I would like to hear thoughts on what > > > this should be, as "Payment" isn't really descriptive and something like > > > "CardProcessing" is too restrictive as the functions can be used for > > > electronic checks and other forms of payment. > > > > What are you thinking of naming the class? > > The class would be named .._Verisign, and I can envisage others such as > .._Cybercash (I understand there is already a Cybercash class in > circulation for use with that extension). > So why not Payment_Versign? <? $ph = new Payment_Versign; $ph->someMethod(); ?> It doesn't mean that other modules can't go under the payment section... -Sterling