dkrauss
Goofy Fan from Jersey
- Joined
- Nov 9, 2013
..............I believe the term that's used is "estimated wait time"So how does Touring Plans get around that issue? or have they changed in the last few months?
Touring Plans?
Doug
..............I believe the term that's used is "estimated wait time"So how does Touring Plans get around that issue? or have they changed in the last few months?
Touring Plans?
Their app says "reported wait times"..............I believe the term that's used is "estimated wait time"
Doug
Who does?They use "Expected" and "Posted"............
Doug
go into the Park (MK for example.........) 7 Dwarfs Train in the list (and yes the park is closed........but there's still a line for 7DMT ) its showing Expected 37 min and just below in a smaller font Posted 45 min........Who does?
I'm looking at TP app now and it says "Reported Wait times" obvs the park is closed now so can't actually check it, but all I'm seeing is reported wait times
It's been a while since I've used it, but Touring Plans uses TWO methods - their own predictive modeling based on past info, and guests using the app to report the posted and actual wait times. I don't think they were feeding off the data that MDX was presenting, but that may have changed.
I know there was one site that was scraping the MDX info somehow and posting it "live". Don't know if it still does. But even then, it's a bit of a different beast - in IT terms, the data is not "time sensitive" - I don't really need to update it every few seconds, forcing a query of the server and thus more load on it. I could grab it every 5 minutes, say, and then everyone else gets the info from me. That's only 12 hits to the servers an hour. Not even noticeable to worry about. And it was probably a "cheap" query - just getting the data already gathered in a cache table (at least if I designed it), as opposed to having to query the various systems for their current data.
I think the issue was that the data stream had two wait times. The Time that was posted and the what Disney thought the real wait time was. So it reinforced the rumor that Disney manipulates posted wait times.
Looks like Dis Dinng Agent got hit. They have a we will be back up next week letter on their home page. WDW Table Finder is still up and acting like nothing it happening.
This place and WDW Table Finder are really not the problem. DiS Dining Agent is the one they need to get.
While the notification service those sites provide is a little more innocuous than DIS Dining Agent...they have to be using bots to constantly search the site for availability. That puts a lot of strain on Disney's servers/IT infrastructure (which we know isn't the greatest to begin with), causing lots of legitimate users to have trouble searching - regularly timing out and getting error messages.
Table Finder is saying no texts or notifications are being sent out since yesterday morning. Although, it looks like you can still do a search on their site.
The post they made on Facebook Tuesday morning says they are honoring Disney's request to shut down. The main web site is still up and doesn't say anything yet though.