>and so on down the line until everyone had bread. At various points, a toaster would finish and would pop up. ... I'd notice that they were done and would run over to give them more toast.
You'd give them more bread, not toast. Toast is already processed bread :).
Technically, Time Based Separation helps only arrivals since it tries to negate the effects of headwinds on final approach, but it does add a lot of resilience to the airport to absorb delays that would normally ripple to departures.
I believe their API is open, and might be able to give you more info based on your actual route of flight. I use them for briefings and notifications, life savers.
I think some folks are missing the point of being able to scale up when needed by just changing the connection string. If you are trying to prove a big data concept with small data, this might be a cheaper path. Now, if there were just standards for NoSQL query interfaces, this might be 100% true...
I have built some pretty impressive AIR apps for our customers (5 apps, 40 KSLOC or so total). It takes a good level of software discipline to make apps that perform, can be reused and are maintainable (like any good desktop app). We chose AIR because of Linux / Window cross compatibility and its beautiful appearance.
You'd give them more bread, not toast. Toast is already processed bread :).