At first glance it looks like Zend_Payment is meant to be an adapter to
the various gateways whereas Chargify sits between your app and the
payment gateway. I'll get in touch with the Varien folks for their
thoughts on a Chargify adapter. I'd definitely be willing to help.
I have a little catching up to do on the state/direction of ZF2. Other
than PHP 5.3 are there any other requirements or conventions I should be
aware of, especially with regards to web services?
Thanks,
-Dan
On 1:59 PM, Matthew Weier O'Phinney wrote:
> -- Dan Bowen<dan@crucialwebstudio.com> wrote
> (on Thursday, 30 December 2010, 07:36 PM -0600):
>
>> I just submitted a proposal for Zend_Service_Chargify and wanted to
>> get some feedback from the community.
>>
>> http://framework.zend.com/wiki/display/ZFPROP/Zend_Service_Chargify+-+Dan+Bowen
>>
>> Is this a component ZF users would be interested in? Does the
>> proposal provide enough detail? Please let me know what you think.
>>
>> This is my fist official contribution to open source. I'm really
>> looking forward to making it a successful one.
>>
> This looks quite interesting. :)
>
> A couple of notes:
>
> * I think a standalone service component makes sense. However, you
> should also contact the author of the Zend_Payment proposal
> (http://bit.ly/f9SBnG -- sponsored by Varien/Magento) to offer to
> write an adapter for that component.
> * As noted by others, ZF1 is in feature freeze, so target ZF2 for this
> component. The easiest way to do so is to fork the ZF2 git repo,
> and create a branch for development of the feature. That will allow
> you to collaborate with others, as well as provide code for the
> Community Review Team to review.
> * Also, move your component to the "Ready for Review" section of the
> proposals, so that folks know you've completed the proposal and want
> comments.
>
> The initial glance I had looks promising!
>
>
没有评论:
发表评论