Because of this, no one ever deploys java on the client-side, unless they
have a tight control over what browser people are using.
I work at a fortune 500 company on a team that is deploying java in a
browser and we have dictated netscape 4.08 and IE 4.01 as the required
browsers.
You're probably better off deploying java on the server-side and using
something like PHP or java servlets as the interface.
Tim Perdue
PHPBuilder.com / GotoCity.com / Geocrawler.com
-----Original Message-----
From: Bob VonMoss <bvonmoss@bigfoot.com>
To: PostGreSQL General List <pgsql-general@postgreSQL.org>
Date: Sunday, April 25, 1999 8:08 PM
Subject: [GENERAL] PGSQL/JDBC & browser compatibility
>I'm developing a java applet with JDBC using the Postgresql driver.
>Apparently, the only browsers that are compatible with my java code
>compiled under Sun JDK 1.1.X is Netscape Communicator 4.5 and the Sun
>JDK 1.1.X appletviewer. MSIE 5.0 gives me the message "no suitable
>driver" when I try to connect to pgsql. There are all kinds of error
>messages, not only with Netscape 3.0, which of course does not support
>the java.sql package, but also Netscape Communicator 4.0.x
>
>Is anyone using pgsql with MSIE? Is there a MS java compiler?
>
>How have others dealt with JDBC and the limited browser selection? One
>solution is to not do JDBC in the front end applet and only in the back
>end which is not used in any browser. This defeats a lot of the purpose
>in using JDBC in the first place. Of course, JDBC is nice from a
>database programming point of view, but sucks because it lacks security
>and won't go through firewalls.
>
>--
>Bob VonMoss
>mailto:bvonmoss@bigfoot.com
>from Chicago, IL
>
>
