Re: How would YOU write a client/server Java applet today?

java400-l-bounces@xxxxxxxxxxxx wrote on 07/27/2004 12:39:31 PM:

> 
> However, I am very interested in the concept of having the Swing applet 
> talk to the HTTP server rather than directly to the database this 
> certainly would resolve some possible firewall issues that we have 
> anticipated (we currently were planning to require VPN access to the 
> server).  If you have any more info on this it would be appreciated!!!
> 

You could probably craft your own solution fairly easily, but the way to 
do this today using tooling is probably web services.  Expose your servers 
as web services and then consume those web services from the Java GUI. 
This also opens up a lot of other long term possibilities as there are 
some nice tools out there for gluing together web services to build 
business processes.

By the way, signing your applet is a security mechanism for the client 
side.  My concern was that for the clients to be able to use JDBC and 
Program Calls those ports on your server have to be accessible.  If this 
were a pure Internet app, that would mean they would have to be open in 
your firewall.  This would make your server vulnerable to attack and would 
be hard to secure and still have your application function properly.

Mark