Letting the User Interrupt
We need to redraw the map of application design. Some of us have done this before.The inexcusable sin of any so-called information technology is failure to pay attention. The 1950s or 1960s model, where jobs get fed to big, dumb beasts that answer when theyre good and ready, must not sneak back into our lives as part of the baggage of distributed services. I recently made the mistake of clicking on a hyperlink to a streaming video resource when I was inside a thin-client desktop, remotely accessing a server at dial-up speed. The same Web site, on the same dial-up line, worked fine with a local browser, but it brought the Citrix client to its knees. Worse still, I could not even get the attention of the clients top-level loop to abort the viewer task. I had to shut down the whole session and start from scratch. Pardon me, my time machine must have sent me back a few decades.
We need to redraw the map of application design. Some of us have done this before: Perhaps I date myself by even remembering flow charts, with their model of "start here, collect input, make decisions and put out the result."