GoFuckYourself.com - Adult Webmaster Forum - View Single Post

Nathan · 10-18-2005, 11:32 AM

Hi wzl,

NATS is written in a very strict manner and is very strictly version controlled. A this big change, which involves changes in member templates, the stats engine and similar things will not be done in 2 hours, thats what breaks stuff.

This kind of thing would be done in a main version release most likely.

While I agree #5, #6, #7 is interesting, there are much more things we can offer to affiliates which are more important to them right now, especially #6 and #7. Also, #5 is already doable, as is #3 and #4, but its only one-at-a-time right now, so you would have to choose one of 3-5 to actually do.

One more thing that totally messes up your whole 2 hour theory is, what do you exactly call a CC attempt, what a CC failure? Is an attempt every single try for each biller in the cascade? Is a failure every single failure for each biller in the cascade? Do we want attempts and failures for non CC transactions? If not, why not? If yes, for which? Also, can we TRACK attempts and FAILURES and even then AVS REASON, or what I would guess makes more sense is failure reason, for each of the over 25 billers we support?
Will billers that can not track failures or failure reasons mess up the value of these stats?

Now, all those questions above need to be answered before we can even START and for many of them each of our clients will have a different oppinion, so they will start asking us to make it possible to turn off some of these settings and not track those that can not track a reason for example, and similar things. Now this again causes discrepencies in our client's stats which people will get confused about and the whole point of this idea went out of the window.

All that the above was ment to show is that nothing always is as easy as it seems.

10-18-2005, 11:32 AM
Nathan Confirmed User Industry Role: Join Date: Jul 2003 Posts: 3,108	Hi wzl, NATS is written in a very strict manner and is very strictly version controlled. A this big change, which involves changes in member templates, the stats engine and similar things will not be done in 2 hours, thats what breaks stuff. This kind of thing would be done in a main version release most likely. While I agree #5, #6, #7 is interesting, there are much more things we can offer to affiliates which are more important to them right now, especially #6 and #7. Also, #5 is already doable, as is #3 and #4, but its only one-at-a-time right now, so you would have to choose one of 3-5 to actually do. One more thing that totally messes up your whole 2 hour theory is, what do you exactly call a CC attempt, what a CC failure? Is an attempt every single try for each biller in the cascade? Is a failure every single failure for each biller in the cascade? Do we want attempts and failures for non CC transactions? If not, why not? If yes, for which? Also, can we TRACK attempts and FAILURES and even then AVS REASON, or what I would guess makes more sense is failure reason, for each of the over 25 billers we support? Will billers that can not track failures or failure reasons mess up the value of these stats? Now, all those questions above need to be answered before we can even START and for many of them each of our clients will have a different oppinion, so they will start asking us to make it possible to turn off some of these settings and not track those that can not track a reason for example, and similar things. Now this again causes discrepencies in our client's stats which people will get confused about and the whole point of this idea went out of the window. All that the above was ment to show is that nothing always is as easy as it seems. __________________ "Think about it a little more and you'll agree with me, because you're smart and I'm right." - Charlie Munger