You need to change the title of this thread to UNSOLVED
Cause yup... it happened again a full 3 days later, lol
let me quote you again
works like a champ!!
~|
ColdFusion is delivering applications solutions at at top
his problem wasnt in the authorize.net component, it was that he is setting the
customer # when the come into the site and and so he had 2 identical customer
#'s, and he obviously isn't checking for duplicate customer numbers either.
Will,
It's still going to bite you in the butt. You still
Look, it happened once out of 860 orders the way it was.
The chances of it happenin now are way less than that. I'll prob still end up
using a guid tho.
~|
Download the latest ColdFusion 8 utilities including Report
it shouldn't happen that once though.
Look, it happened once out of 860 orders the way it was.
The chances of it happenin now are way less than that. I'll prob still
end up using a guid tho.
~|
Get involved in the
And if two people on a NAT router order at the same time?
:-P
On Nov 22, 2007 2:57 PM, Will Tomlinson [EMAIL PROTECTED] wrote:
After consultation with the disruptor, I came to the conclusion that using a
timestamp wasn't a good idea for a customer ID. :) It finally bit me in the
butt after
naw that would never happen..
Funny thing is that is what he said to me when he first used just the
timestamp, lol
And if two people on a NAT router order at the same time?
:-P
~|
Download the latest ColdFusion 8
Will,
It's still going to bite you in the butt. You still have a race condition,
and lots of people share IPs. From what you've said, I'd say take a good
hard look inside the AuthorizeNet component. Or lock the bejeesus out of
it - but if you just do that it's going to be hard to know whether
7 matches
Mail list logo
