|
Re: Business::WorldPay::Junior and last release date
by jkeenan1 (Deacon) on Dec 27, 2005 at 14:13 UTC
|
Should we be bothered, as this probably just means that no new features have been added or that there are no new bugs and that it's stable.
It could mean those things. Or it could mean that the module didn't prove very useful to anyone, in which case no one has been concerned as to how well it works.
Two things you can do: (1) Download the module and test it with Devel::Cover to get coverage stats. If the coverage is high, that doesn't necessarily mean the code is bug-free (as I've learned the hard way with my own modules). But if the coverage is low, it means the author didn't thoroughly test the code in the first place -- which doesn't mean that it's not useful or has bugs, but simply that there are more unexplored places where bugs might be lurking.
(2) Contact the authors and see if they're still using and supporting the code.
Jim Keenan
| [reply] |
|
|
Business::WorldPay::Junior
My perl module for those using the WorldPay Select Junior payment proc
+essing service.
The module provides a simple interface to track transactions and to ha
+ndle callbacks from WorldPay to verify the transaction has been autho
+rised and the right amount has been paid.
Full documentation is included with the distribution.
Do note that you must read the README file. The installation is a litt
+le more involved than just running make, make install as you often do
+ with Perl modules. The module is dependant upon MySQL and the DBD::m
+ysql module.
The distribution also contains a script to keep your installation up t
+o date with the WorldPay exchange rates. This script should be run ea
+ch evening to get the next days working rates.
There is a £ 25.00 charge for this software. After you pay the charge
+you will be provided with a link from which you can download the late
+st version (1.05) of this module. To pay click here. Yes the process
+does use the module to handle the payment.
The module is licensed under the terms of the GNU General Public Licen
+se. If you want to use this module in a software package that is not
+compatible with the GPL license contact me to discuss alternative lic
+ensing arrangements.
Do you think we should be paying the £25, when it's version 1.0.7 that is on the CPAN?
I think we will e-mail him.
Gavin.
Walking the road to enlightenment... I found a penguin and a camel on the way.....
Fancy a yourname@perl.me.uk? Just ask!!!
| [reply]
[d/l] |
|
|
Hi Gavin,
I would suggest to contact the author. Maybe the module is now available in version 2.0 or it is available for free now.
If you cannot contact the author/maintainer, I would seach in Google for that module. Maybe, you can find useful hints there.
my $cents = 2;
Renee
| [reply] |
|
|
|
|
|
Re: Business::WorldPay::Junior and last release date
by mitd (Curate) on Dec 27, 2005 at 18:38 UTC
|
I would go ahead. The callback method used is the 'older' traditional method payment gateways handled web-based transactions and hasn't changed at all in some time..
My expertise is with PSIGate and SecPay but you might check if WorldPay has a newer SOAP or RPC interface which (amongst other features) makes it unnecessary to send customer to gateway site and have to handle callback.
mitd-Made in the Dark
I've always been astonished by the absurd turns
rivers have to make to flow under every bridge.
| [reply] |
|
|
Alas, WorldPay Junior is a piece of shite. Their support sucks, and the callback API is utterly crap. If you want to take the customer details yourself and then pass it to WorldPay behind the scenes, then you must use either WorldPay's Java or their Microsoft COM APIs. You'd think that in the 21st Century, they'd have heared of SOAP.
| [reply] |
|
|
| [reply] |
|
|
|
|
|
|
That is not my experience: I have analysed the WorldPay callback process carefully, and have been able to satisfy myself that it can be made secure, which isn't always the case.
Maybe our needs are different, but I had no problems coding to it, and our clients have reported no problems getting support or getting their money.
They are not the cheapest payment processing service out there, but the cheaper one that I investigated at a client's request turned out to be entirely insecure (ie there was no way to write the client code so that the callback could be confident the ordered goods had been paid for); when I pointed this out to them they agreed, but affirmed that they had no plans to change it.
Hugo
| [reply] |
|
|