Adam,
I was interested to find your "ticket splitting" application (mostly from a mathematics and computer science perspective). I see that you intend to offer split ticketing advice for Advance fares. However, from my understanding, a comprehensive comparison of intermediate fare combinations would require an unreasonable number of real-time queries to whichever external database would maintain such information. I recognize that such comparisons would be relatively trivial in the case of locally-stored static fares, but I doubt any live fare datafeed would be prepared to take on the volume of simultaneous queries necessary to fully examine Advance fare splitting options. I am curious to know how you are approaching this problem and whether you have an idea of when a more fully fleshed out version of your application might come to fruition.
Regards,
Nathan Johnson
[email protected]
I was interested to find your "ticket splitting" application (mostly from a mathematics and computer science perspective). I see that you intend to offer split ticketing advice for Advance fares. However, from my understanding, a comprehensive comparison of intermediate fare combinations would require an unreasonable number of real-time queries to whichever external database would maintain such information. I recognize that such comparisons would be relatively trivial in the case of locally-stored static fares, but I doubt any live fare datafeed would be prepared to take on the volume of simultaneous queries necessary to fully examine Advance fare splitting options. I am curious to know how you are approaching this problem and whether you have an idea of when a more fully fleshed out version of your application might come to fruition.
Regards,
Nathan Johnson
[email protected]