Echo2 Framework

It seems the Echo2 framework transmits down to the client any changes it perceives occurred based on calls to add/remove/set methods of its components. What this translates too is that Echo2 does not keep track of what has already been transmitted in order to conserve bandwidth, so my code has to do it instead.

This isn't too surprising really. I had it in the back of my mind that this is how it likely worked. It is a little annoying, but I can see where such a self optimization would be complex to implement without doubling the memory requirements per user.

Initial testing shows that dial-up users are extremely vulnerable to excessive refreshes. It doesn't take too many before the "please wait" screen starts popping up. In fact, based on how the chat rooms behaved, I'd say it might be a good idea to reposition that "please wait" screen to somewhere other than the center of the screen. Perhaps the top-right.

I do hope Echo3 gets released soon. Support for dial-up is important.