Quote:
Originally Posted by PaceAdvantage
I heard an executive once from another ADW claim that "hardly anybody uses conditional wagering."
Maybe that's why it is so low on the priority list. Also, I'm thinking conditional/batch wagering uses too many system resources. Especially on big days.
After all, conditional wagering was one of the first things that WENT DOWN on Derby day this year at TS. I know...I was still using conditional wagering back then.
|
Can't speak to conditional wagering, but wouldn't batch wagering actually decrease resource use? You're not opening up a connection for each wager. As it is with TS, if I want to submit wagers for Tri/Supers programmatically, I call the bet request once per merged ticket. This can mean > 100 requests for a race. Compare that to AmWager, where I send once. Until about a month ago, I wasn't even aware that TS offered batch wagering - wish I had known as looping through wagers one at a time has actually caused me to miss placing some tickets.
On a different note, Spicemaster, thank you for taking the time to engage with the forum, and I hope you continue to do so. Having reps from the various ADWs lurking around here has only up side. BTW, to those questioning his sincerity, it is totally believable that this feature was broken and has not been prioritized to be fixed. My guess is that TS primarily caters to recreational players, given the rebate levels, and that recreational players likely are not huge users of batch wagering. Again, a total guess. But if that's the case, and imagining that they have an active issue list with 100s/1000s of issues, I can see how something - even if it only may take a few hrs to a day to fix - is low priority. Regardless, as a VIP rep, Spicemaster isn't the one prioritizing tech issues...
