The problem with Java Applets is that most browsers disallow network
connections to any machine other than the machine that the applet was
downloaded from. These issues have to do with security and while there
are legit reasons for wanting to connect to other machines the applet
standard has never made strong requirements or specifications for
telling a browser to allow such services. They are working on it.... not
that it helps you know :)
What Stuard Urban suggested in his email is a way of going about doing
it. This would work well if you had the data access objects on a single
machine and sever client servers for the applets on multiple webservers.
This would allow for updates to the query java code without propogating
the changes to several machines.
A slightly easier solution would be to just write a java application
that runs on the server and connects using jdbc to the database
directly. This does not have the benifit as the above mentioned solution
though.
Chris Ryan
doug@dupreeinc.com wrote:
>
> Hello,
>
> This question is not exactly on topic, but I hope someone here can point
> me in the correct direction.
>
> I have a postgresql database on machine1 that works fine. I have a
> applet served by machine2 that needs to reference the postgresql
> database on machine1. how do I go about doing this? My applet works
> fine in the JBuilder Applet viewer, but it will not run on the live
> systems. I think this is because of a browser security violation, but I
> have not been able to find a work around. Please let me know any
> suggestions you may have on how to make this work.
>
> Thank you for your time!
>
> Doug T.