Agreed. Though ours took a little longer to develop because of other requirements (tweaking to tune the performance, though, took a bit. Getting the best performance out of the back-end was a high priority given that it was supposed to provide real-time data. That wasn't completely trivial.).

Dan

Oh, so you *didn't* write the back-end as well. I didn't have to write the applet (though I helped a little). My job was to write the back-end. To me, that was the interesting thing (designing it for extensibility and performance at the same time).

To be honest, my javascript/DOM skills aren't good enough to do it that way (and no one else here has them, either). I know it can be done, and know, generally, how it could be done, but that's about it.

As for "optimize no sooner than necessary"....though I agree (since the statement is written such that you can't really disprove it), optimizing sooner, rather than later, isn't a bad thing, necessarily. The flip side...optimizing later on (on purpose) can put you into a position where you *can't* optimize without big changes (and that's one of the problems that we have....to integrate it with an existing, non-optimized, internal application).

Dan