My contention is that it'd be more swallowable to do a telnet and a full-on 3d engine rather than trying to do a telnet and a web based engine. Graphics are graphics, and if you're gonna do them then using an engine which really shows 'em off seems like the best play. The "true browser based" you cite above doesn't allow offloading enough of the processing onto the clients to give an experience worth spending lots of time and money in development.
Server Push: Points taken, the problem is it still depends on browser support and needs frames (lest you get a new push midway through filling out a form). Doesn't do anything to help the aforementioned WebTV users or me on my wireless Palm and such.
On Flash: Most estimates put Flash market penetration at around 94% right now (had to look at this 'cause we're trying [grumble] to use Flash as an interface for some web tools). So using Flash limits market probably about the same as server push or frames or even PNG (which hasn't been supported that long).
My contention is that it'd be more swallowable to do a telnet and a full-on 3d engine rather than trying to do a telnet and a web based engine. Graphics are graphics, and if you're gonna do them then using an engine which really shows 'em off seems like the best play. The "true browser based" you cite above doesn't allow offloading enough of the processing onto the clients to give an experience worth spending lots of time and money in development.
Server Push: Points taken, the problem is it still depends on browser support and needs frames (lest you get a new push midway through filling out a form). Doesn't do anything to help the aforementioned WebTV users or me on my wireless Palm and such.
On Flash: Most estimates put Flash market penetration at around 94% right now (had to look at this 'cause we're trying [grumble] to use Flash as an interface for some web tools). So using Flash limits market probably about the same as server push or frames or even PNG (which hasn't been supported that long).