We've just touched down in Saint Louis at 10:25, about 25 minutes late. My connection leaves in minutes, and it's the last flight of the day. The captain has radioed ahead to hold connecting flights to Las Vegas and San Francisco among others, but I don't hear anything over the PA about my connection to Kansas City. I'd really like to know what gate I need to be at in 14 minutes.
Never fear: I know the OAG publishes real-time flight status info, so using my PDA and cellphone, I pick TWA and enter the flight number and seconds later, I get the critical info I need: D14(@@double-check).
And it's a good thing I didn't need to wander around looking for that info after deplaning: the agents on the ground were all busy and D14 was, in fact, all the way across the airport terminal from C18(@@) where we arrived.
I tucked away my gizmos, hiked across the airport, and boarded just before the doors closed.
Sounds like a WAP success story, right? A special WML web site; designed-form-mobile network protocols, and all that? Wrong. This success story is brought to you by the 5/10 year old buzzwords: TCP/IP, PPP, HTTP, HTML.