In a three-tier application such as the one you describe, you generally have
a user interface, a middleware section that includes the application logic,
and the database component.
The trick is the determine where the bottleneck is (that is, where is the
bulk of the communication taking place). If the application middleware layer
is frequently accessing the database and requesting large amounts of data,
it would make sense to put the middle layer at the server side and use plain
html on the client front end. If however, the bulk of the interaction is
between the user-interface and the middleware layer, then it might make
sense to stay with using an applet to enable greater processing on the
client.
Regards,
Tony
> -----Original Message-----
> From: Joe Blow [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, June 23, 1999 2:12 PM
> To: [EMAIL PROTECTED]
> Subject: Which one is better ?
>
> Hi all ,
> I was earlier using applet/servlet combination for a Web based
> reporting system.applets formed the front end.servlets handled the
> database
> access part.
> What I am investigating now is whether I can improve the speed of
> the application
> by using the JSP/servlet combination or not.
>
> Do you guys have any opinions in this regard ?I would be pleased to
> hear from you all.
> Thanks in advance ,
> - Mahesh.
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
