Re: CTXS and Java
jkb,
Okay. Now I can make a stab as to why ICA is better than Java.
For Oracle's i initiative, there does have to be a Java, "interpreter," on the client. Albeit, it's small. But the bigger drawback is the size of the Java app being sent down to the client. I'm guessing the more complex the app, the larger in size it is.
Even though I have a cable modem, I notice when Java apps are sent to me, there are long delays(meaning 15-30 seconds in my case). I noticed the fancier the app, the longer it takes. As time goes by, the apps get fancier. When has anything become less complex in the computer world?
My feeling is even though Java apps are supposed to be tiny and easily processed, I am ALREADY noticing more and more time delays from just one year ago. And not being a programmer, I'm wondering if that once tiny, "interpreter," is growing in size and complexity also.
If CTXS does manage to create a Metaframe Java compliant server, then I can see how that would be valuable. If processing/intepreting is done on the CTXS server, once again it only needs the latest, greatest processor and tons of RAM. And the client can truly remain thin because it only needs to do the good old screen refreshes.
And of course, using Java Metaframe, clients can still be connected with that tiny 28.8 pipe and have full blown access to the latest, greatest Oracle i stuff with less delay than I experience now.
MikeM(From Florida)
PS jkb thanks very much for your interesting Java discussions and comments. |
