Re: Re: Preferred way of generating XML in pear packages?
| From: | Philippe Jausions | Date: | Tue, 05 Apr 2005 18:20:13 +0000 |
| Subject: | Re: Re: Preferred way of generating XML in pear packages? | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37098@lists.php.net to get a copy of this message | ||
James Carr wrote:
On Apr 5, 2005 5:51 PM, Philippe JausionsThis is exactly what Payment_Process does. Takes a transaction, sends it for processing, returns a result (in the form of an object.) Although, I agree with you, maybe the processors should be spun off into their own packages to help maintenance by multiple people. However, due to the beta status of the Payment_Process that may be too soon to do so this way. The idea behind Payment_Processor is to be able to switch payment gateway without having to change too much code in your application. Of course, due to the nature of a common interface to all payment gateway, maybe not all features would be included. But it is worthwile making all the processor using the same API. -PhilippeJames Carr wrote:Currently I have a custom class I had used for some gateway intergation I did for a few clients, basically all it does is send auth transactions and returns the response as an array. Although I have been toying with the idea of implementing the full feature set, perhaps those should just be seperate packages?I'm currently touching up my payfuse/clearcommerce package to submit as a proposal, and I'm curious what is the preferred method of generating XML in pear packages? I am currently using DOM, but am wondering if I should shy away from it due to the differences in implementation between php4 and php5?Please consider making a backend processor for Payment_Process package instead of creating a whole new package.