Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Applet or Web based app?  RSS feed

 
Jerzi Deflanax
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I like java and use it in several desktop and server application, but now I am designing the architecture of an internet open application.

I think that due to its openness, it should be a web application instead of an applet application.


I feel that it should be a non-applet application, but I would like to receive your commentaries.

Kind Regards
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's hard to determine if an application should be web based, applet, or anything else without having any information on what the application is and does. All you did was tell us you think it should be web based.
 
Jayesh Lalwani
Ranch Hand
Posts: 502
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The rule-of-thumb for me has always been try to implement web-based as much as possible. If you can leverage functionality provided by HTML and Javascript, the use it. If your application needs to do something on the client side that Javascript cannot do like communicate over a socket, use Open GL, upload multiple files, etc, etc then write an applet
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jayesh Lalwani:
The rule-of-thumb for me has always been try to implement web-based as much as possible. If you can leverage functionality provided by HTML and Javascript, the use it. If your application needs to do something on the client side that Javascript cannot do like communicate over a socket, use Open GL, upload multiple files, etc, etc then write an applet


I can't agree with that 100%. Just because something can be done with a webapp, doesn't mean it always should be. Again, we need more information before any intellegent response can be made about your question.
 
Jerzi Deflanax
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you for your kind answers.

The main characteristics are:
The application is used by each users a couple of times each year
The application should be highly scalable (The application is used mainly in a seasonal fashion <Christmas>
The users are very heterogeneos (again think in an ecommerce site in the Christmas season)

Hope this makes my question more clear.

Is there any big open (non intranet) site that uses applets?
Kind regards
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So let me get this clear. Are you saying this is between a completely HTML based webapp (probably J2EE backend stuff) versus a web page with Applets on them? We aren't talking Client Desktop app vs Webapp then, right? If that's the case, I will always say no to Applets.
 
Jerzi Deflanax
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

That is exactly the case.
It is a Web application to be used remotely though Internet.
The choices are:
An Applet based application (powerful client, very interactive, a single big post)
A javascript/HTML/CCS application (simple, familiar, several small posts )

The backend is the same for both choices.


May you tellme why you dont recommend the applet option?
Regards
 
Jayesh Lalwani
Ranch Hand
Posts: 502
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think the question to ask yourself is

1) Why do I need a powerful client?. Is there some processing going to be done on the client side that cannot/should not be pushed to the server side? Generally speaking pushing processing to server side is less costly (in terms of dollars) than processing on the client. Unless your clients need dedicated use of the resources (like running a big number-crunching program that uses 90% of CPU), it's more cost-effective to have the server process the information for multiple clients. Besides that, if your application is database centric, then most of the work is going to be done by the database anyways. It's better that you push off the code that accesses database to the server so you reduce network latency

2) Do I have thick clients available? The most common complaint with applet-based webapps are that applets are too slow and resource-intensive compared to browsers. If you are developing your application for the general populace, then people are going to complain that the applet takes time to downoad, start and run. Plus, if you want a decent SWING UI on IE, then you need to download and install the Java plug-in to the clients. That creates even more headaches
 
Jerzi Deflanax
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you all for your help.

I tought that the web based solution was more suitable, your opinion have been very valuable.

Kind Regards
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just for my 2 cents I'll +1 everything Jayesh said.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!