2 ms·
The frontend assumed the backend was fast enough. That's the problem. If the frontend was made to handle really slow responses from the backend it would look
by ape4 13y ago
The frontend assumed the backend was fast enough. That's the problem. If the frontend was made to handle really slow responses from the backend it would look different. It would not make people wait while transactions occurred. Or if might have a page that that displayed your progress: in other to do this for you we need to contact 10 databases - here is the progress of each:
Database One: [=======----------]
Database Two: [============-----]
Database Three: [==---------------]
- hga 13y agoHeh. But I would half joke that that would result in a bunch of angry people with torches and pitchforks showing up at sites of the owners of Database Two.... Which might be totally unfair if it's not really their fault.
- ape4 13y agoMy ASCII graphics were trying to show Database Two as fast and Database Three as slow. That's where the pitchfork toting mobs should be.
- hga 13y agoOh, yeah, progress toward completion, which would obvious to most everyone using the site. But I'm sure some would get it wrong even then! Visions of a family gathered around the monitor: "Go IRS!" "Social Security, we KNOW you can do it!" Etc. (I do really like your idea, it just seems to be inevitably politically impossible.)