> Yes, he might run into security problems but note that normally Sockets can
> be connected from an applet back to the host where the applet was downloaded
> from.
Yes, of course.
> So, if your database and your web server are on the same host, you are
> in luck.
Not really since this makes the application highly deployment dependent
and it is generally not good to have db and app server on one machine - at
least if you target for higher server loads.
Apart from that, it does not address the firewall problem. So your applet
might happily try to connect to the db server, but the firewall might eat
the network packets. :-)
> But if your database and webserver are on different machines, you
> will need more security privileges. That is standard stuff regarding
[quoted text clipped - 5 lines]
> called the Java programming language can't guarantee that a security
> violation won't occur.
An important piece of information.
> The "No suitable driver" is an exception that, most likely, occurs when
> calling the DriverManager.getConnection method. This is because you couldn't
[quoted text clipped - 5 lines]
> does. So tunneling the database calls is a better approach and that also
> allows you to change the datasource without redistributing the applets.
And it can be slow depending on the data to transport and the db vendor's
protocol implementation. If you restrict the data that has to be sent
over the line by the necessary data, it is likely that performance goes
up.
robert