Re: Java servlet on browsers: dying or kicking ?

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 28 Dec 2012 11:07:31 -0500

Message-ID:

<50ddc3cb$0$291$14726298@news.sunsite.dk>

On 12/28/2012 12:13 AM, Gene Wirchenko wrote:

On Thu, 27 Dec 2012 21:07:02 -0500, Arne Vajh?j <arne@vajhoej.dk>
wrote:

On 12/27/2012 2:20 AM, Kevin McMurtrie wrote:

In article <op.wpt8ogiewv4027@kiat-1>,

Ha, my mistake; "servlet" should actually be "applet". Thanks for
correcting me.

Definitely in decline. HTML 5 + WebSockets can make fully interactive
applications that look and feel native. The improvements are so great
that the dreaded workflow and business logic tier can be moved from the
server side to the client side. Moving that tier to the client takes a
HUGE load off the server, making the server a pure number cruncher and
data service.

Business logic should not be put in client side JS.

I disagree. Client-side logic makes for quicker UI response.

I don't think there is much point in having business logic that is
not enforced.

And client side logic can not be enforced in a web solution.

Client side JS can be manipulated by the user.

But since this is also true, put the logic in the server side,
too.

I don't think there is much point in implementing all the business
logic twice - server side in Java and client side in JavaScript. That
would be an awfully waste of money.

But I think I know what you are thinking about. You are talking about
data input validation.

There are good reasons to do that both client side (for smooth UX) and
server side (for security).

But the overlap between data input validation and business logic
is pretty small. Most business logic is not data input validation.
And a big chunk of data input validation is really UI and not
business logic.

Arne