Mr. Coffee TCX85 User Manual download pdf (Page 18)

BTW, the JavaStations, now that they are fast, are quite fine. I really like mine, and

don't see why they aren't a viable product.

−−Dr. Mark Barnard, Professor at Marquette University <[email protected]>

I believe that it was the triple combination of Sun's JavaOS, the Hotjava software, and

GraphOn's GoJoe X−connectivity software which ultimately doomed the JavaStation

line.

JavaOS was always sluggish in performance for us. It was rated as having one of the

slowest Java VMs by a ZDNet Online Magazane review at

http://www.zdnet.com/pcmag/features/javaguide/hfgr10.htm . I speculate this was the

the main cause of delaying the JavaStation's formal public release to April 1998.

JavaOS also always lagged behind the current Java developer spec (ie running Java 1.0

when Java 1.1 was prevalent, and Java 1.1 when Java 1.2 was issued). It was tough

explaining to students why the books they were buying were all using the new

event−model of Java 1.1, but they could not program to it and have it run on "the Java

machine". There were also some implementation problems with some of the AWT

peers which sometimes made programming across platforms difficult.

These performance and implementation problems were never addressed in subsequent

build of JavaOS for the duration we ran it. I believe the last edition we had used a Java

1.1.4 runtime, when we had a Java 1.2 development kit on the server.

The HotJava browser software suffered from not being able to handle web standards

HTML4, cascading style−sheets, or the ECMA javascript. All of these standards were

employed in commercial sites at the time, resulting in many sites that weren't viewable

by the JavaStations. The Hotjava Browser engine also had serious printing problems

with certain webpages, some of which appeared on Sun's own website!

The HotJava Views task selector software also was rough. Users could have multiple

apps running, but only one displayed at a time. Manipulation of multiple window panes

was difficult (no minimization, no quick list to all apps, resizing not always possible).

Flexibility users had grown accustomed to was tossed out in favor of this task−selector

approach. On Sun's Java website there was a page boasting of a committee formed that

decided this was the "right way" to make a desktop. Tell that to our users.

The GraphOn Go−Joe software was by far the most damaging piece of software to the

JavaStation line. This was an X−connectivity software Sun licensed from GraphOn to

give users access to the Solaris servers' X apps. The connectivity worked via a daemon

installed on the Solaris server, which was connected to by a Java connectivity applet on

the NC side. This small applet (only about 250K) simply threw up the latest display

state and sent back to the daemon the mouse and keyboard strokes of the user. Unlike

Xterminals though, the actual Xserver process was spawned and communicated with on

the remote server−side by the daemon. Communication between the GraphOn client

applet and the server daemon was supposedly done by a patented protocol to compress

communication and speed things up. However, the performance of X under Go−Joe

was terribly sluggish, with horrible refresh rates (10−seconds for some page scroll

refreshes). Many sites operators I spoke to elected to not run the Go−Joe software past

a trial period for this reason. We had to run it though, as our users were heavily X

Linux on the Sun JavaStation NC HOWTO

Why JavaStations are No Longer Produced 15

1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 42 43

Comments to this Manuals

No comments

Mr. Coffee TCX85 User Manual Page 18

Comments to this Manuals

Related products and manuals for Coffee makers Mr. Coffee TCX85