"The problem I see with their argument is that they are making this information public."
I love this idea! However, I think that unfortunately this argument doesn't hold up, and wouldn't in court. The information is available via their site, but that does not make it public.
If the info is on the web it's available to be consumed by humans or robots in a polite manner.
Data wants to be free.
Them trying to enforce their terms is another matter. Maybe it would hold up in court. Stupider things have. I mean they should start telling us how to breathe air next. Because ya know if it's in your terms then it must be legally binding.
> The information is available via their site, but that does not make it public.
Could one offer fair information if there's no reference to Southwest? Is having a website full of listings like "flightno: 123, flight_datetime: 2018-03-04-1045, price: 234.56, price_datetime: 2017-11-15-1130" something Southwest could successfully block?
If you got the info by scraping Southwest's site, I don't think it will matter if you present it without reference to Southwest. You're in trouble for how you got it, not how you present it.
The existence of the request itself (for the handshake) is most of the cost. If a client is on the other side of the world, hundreds of ms. Otherwise if you have servers everywhere, still probably 50-70ms for the handshake.
I will never use eBay again. It took over a month to get a refund for a product that was never shipped. In fact the transaction was somehow canceled by the seller within minutes of it being completed, but it still took a ton of work on my end to get the refund. What a shame
Thank you! This is just Promise.all but for microservices. Every time a large company discovers that its messy infrastructure can be cleaned up a bit by reimplementing a simple programming concept, it's suddenly not just newsworthy but framework worthy