Just to play the other side of the argument here...there are lots of technical ways to make things more and more secure. The downside to almost all of them is that it also makes the process more difficult. I've seen a bunch of clients over the years that get fixated on making things "totally secure" and completely lose usability in the process. Trying to root out the possibility that 1 in 100 people might dick you over can result in another 20 never bothering to go through with their purchase because you made it too difficult. Yeah, you made it "more secure" but you lost more than you gained and that should always be the bottom line.
There's a reason that stores figure shoplifting loses into their pricing models. Work on finding and preventing the big stuff. Don't sacrifice usability for the sake of trying to prevent every last little thing. Just something to think about as you meet with them. Cheers, Judah On Thu, Aug 9, 2012 at 5:37 PM, Bruce Sorge <[email protected]> wrote: > > Yeah, I have a bit flag in the DB for the barcode already, so when someone > registers and they are given a barcode, then I flag it as being used in the > barcode table. 0 > Anyway, as I said earlier, I have a meeting next week with the client and I > am sure that this issue will be resolved then. I am just thinking ahead. > > Bruce ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:353600 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm
