Re: how did we miss Echo?
Alex Russell <[email protected]>
| Newsgroups | gmane.comp.windows.devel.netwindows |
|---|---|
| Organization | netWindows.org |
| Message-ID | <[email protected]> |
On Tuesday 09 September 2003 20:40, Andrew Tetlaw wrote: > It doesn't appear to be as 'spiffy' as netWindows, though. It uses a > hidden frame for server communication and basically redraws the page for > each action. In their defense, we also use a hidden frame for communication as well. We add some smarts to it by making a queue around it so that it doesn't get "distracted", but the basic technique is the same. > I was dissappointed when table column sorting required a > round-trip, when there are quite a few dhtml table sorting scripts easily > available. Yeah, that's kinda janky, although if they're trying to keep extending the paradigm of keeping _all_ the interface state on the server and making the web-side of it just an in-time rendering of that interface, then it make some sense for them. I dissagree with it as an architectural choice, but that's just my opinion. > So it seems the JS interface capabilities are pretty thin. I guess the more I look at it, you're right. If the decided to bone-up on that side of things though, they could do some pretty neat stuff. > Maybe you guys should meet with those guys and have the best of both > worlds! I don't know how well it would work. We're all about letting the client side handle client UI state, and their entire premise seems to go against that. But it can't hurt to talk. -- Alex Russell [email protected] BD10 7AFC 87F6 63F9 1691 83FA 9884 3A15 AFC9 61B7 [email protected] F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46 _______________________________________________ The netWindows developers list: [email protected] http://netwindows.org/mailman/listinfo/devel_netwindows.org