> 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 don't know that I see that much difference between the two
cases, except for scalability requirements. The next release of
the product is supposed to contain a supported web server (the
first release just had a demo version), and is also supposed to
support native compilation of user code.
> 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.
I see lots of IBM announcements on the web and in news articles,
so it doesn't seem that big a secret to me.
> 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?
Yes, but the model that I've heard as the default is that the
user will connect via HTTP, and for dynamic content the server
will be running a servlet that will build the JDBC results into a
web page. For static data, I supposed that it would come from the
file system, tables, iFS, or get handed off to an Apache server
or something.
> 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)
That's why the logic is all on the server. So the stuff on the
pipe is just what you see in your browser. If you want something
fancier, you can use IIOP and write an applet, or wait for
XML... |
