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

java400-l-bounces@xxxxxxxxxxxx wrote on 07/27/2004 02:53:25 PM:

> 
> I obviously do not know all of your business requirements so it is hard 
to 
> pass judgement, but I think you are heading down the wrong path.  My 
> primary concern, is that I think it is a mistake to allow the clients to 

> talk directly to the server.  Even if you use Swing, I would recommend 
> that the client talk only to the application server over HTTP/HTTPS and 
> that the server then execute the business logic (JDBC, program calls 
> etc..)  Otherwise, I think you are opening up a lot of potential 
security 
> and deployment issues.
> 

I just re-read this and wanted to clarify something.  If someone were to 
say they were going to write a fat client Swing app (which is essentially 
what you are saying) that uses jt400 to run JDBC and ProgramCalls, I would 
not have any specific concerns about that.  I think all of the technical 
pieces are fairly sound.  This is more or less what we are doing in our 
applications, we are just using Eclipse/SWT instead of Swing for the 
framework.

It is just that since you specifically talk about delivering it via a 
browser, it implies that this application has reach that extends outside 
of your internal network, or at least could someday.  In that scenario, I 
think you would be better off if you only let the client and server 
communicate via HTTP/HTTPS.

Mark