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

[dclowe@xxxxxxxxxx]

Ok,  really I was only planning on using the browser as a deployment 
mechanism for our internal users, it could have all been done as a fat 
swing client in the first place (in fact our previous Java project is 
deployed in this manner) but that's not to say 100% that we would never 
deploy to remote users, I think if we did it would have to be through VPN 
anyway.  For all intensive purposes on this thread assume that this is a 
fat client but I want the browser/plugin to be my deployment mechanism so 
I am making it a signed applet.





Mark Phippard <MarkP@xxxxxxxxxxxxxxx> 
Sent by: java400-l-bounces@xxxxxxxxxxxx
27/07/2004 04:38 PM
Please respond to
Java Programming on and around the iSeries / AS400 
<java400-l@xxxxxxxxxxxx>


To
Java Programming on and around the iSeries / AS400 
<java400-l@xxxxxxxxxxxx>
cc

Subject
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


--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) 
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.