Hardly,
Thanks. Great response.
I understand 8i is another version of the RDBMS, but I didn't make myself too clear in my post. The Java version of Oracle8, "purpose," was confusing to me. Now it's a little more clear after reading your comments.
Can you tell me who is the target for 8i? Is it for enterprise customers to deploy over their Intranet? Or will it be purchased by customers for them to deploy database information, via a browser on an Extranet? I still don't quite get who the target is for the 8i product. Maybe it's something that can't be answered until they start selling a lot of product?
I knew that IBM was devoting tremendous resources to a Java project, but really didn't know what they were doing. To tell you the truth, we hear so very little about it, I thought they may have dropped it. And this kind of has me concerned about Java's future. But apparently they are still working on it? I wonder why IBM keeps it so under wraps. Seems like they would promote the heck out of it to keep the Java furor alive.
You also addressed another concern I had. That is speed. You say JDBC access is much faster if you are "inside." I believe I understand what you are saying. But say once the JDBC does it's thing, and you are on the LAN(not even considering the Internet) with a browser. You hit the database, then you want results. But don't you still run into that same old snag of having the Java applet being sent down the pipe to do the processing. It's not only slow, but tends to crash the browser. And each time you have to re-access the database, the JDBC on the big iron maybe doing great, but it still has to spit the results down to a client's browser for processing, right?
I know the crashing problem can be eventually solved, but what about the speed, back and forth, down the pipe? How is this ever going to be worked around? Or is this the $64,000 question?<G>
MikeM(From Florida) |
