curl或fsockopen为paypal ipn [英] curl or fsockopen for paypal ipn
问题描述
一个有什么优点? Paypal建议使用 fsockopen
,但是有很多脚本在互联网上使用 curl
。
What advantages does one have over the other? Paypal recommends using fsockopen
however there are many scripts on the internet which use curl
.
我应该使用哪一个?
Curl: http://www.namepros.com/code/306043-process-paypal-ipn-with-curl.html
fsockopen: https://cms.paypal.com/uk/cgi-bin/?cmd=_render-content&content_ID=developer/e_howto_admin_IPN实施
fsockopen: https://cms.paypal.com/uk/cgi-bin/?cmd=_render-content&content_ID=developer/e_howto_admin_IPNImplementation
推荐答案
我真的不认为这是重要的方式,除了在某些Apache2安装可能会有可用性问题(Curl没有安装)或OpenSSL双初始化问题(Curl的SSL初始化失败,因为OpenSSL已经初始化)。
I don't really think it matters one way or another, except that in certain Apache2 installs there could be either availability issues (Curl is not installed) or OpenSSL double initialization problems (Curl's SSL initialization fails because OpenSSL has already initialized).
最近的Apache / PHP设置解决了这个问题,但是一个很好的时候,默认的Apache2 / PHP / Curl安装在Debian不会工作正常,并且PHP流选项( fsockopen
,file_get_contents`)将始终有效,因此我认为文档(2010年7月更新,如果文档上的日期是右,这意味着它写得更早)可能只是想保持简单。
Recent Apache/PHP setups solved this issue but for a good little while the default Apache2/PHP/Curl installs on Debian wouldn't work properly, and the PHP streams options (fsockopen
, file_get_contents`) would always work, so I think that the docs (updated in July 2010, if the date on the doc is right, which means it was written even earlier) may just be trying to keep it simple.
这篇关于curl或fsockopen为paypal ipn的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!