Win a copy of Practical SVG this week in the HTML/CSS/JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

VB Vs JSP

 
Gaurav Jain
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For a project requirement we are proposing the front end to be in JSP where as the client suggests that the front end to be in Windows Forms(VB) and back end processing to be in Java and then build an interface between them.
To proceed with front end in JSP we need to come up with solid reasoning so as to why we want to use JSP instead of VB.
Appreciate if i can get some pros and cons for the same.

[Bear edit: not so urgent]
[ January 10, 2005: Message edited by: Bear Bibeault ]
 
Jason Menard
Sheriff
Posts: 6450
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm urgently moving this post to the JSP forum where it will more readily receive urgent attention.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35750
412
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Gaurav,
I think the real question is whether the application will be a Windows client or a web based app. How much control do you need over the app? Does portability matter? Essentially these things are up to the client.

ps - It's best not to put "urgent" in the subject. Everyone's questions are important and some people don't read posts labeled urgent.
 
Bear Bibeault
Author and ninkuma
Marshal
Posts: 65535
108
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As a favor to the OP, I have removed the "urgent" from the title.
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You are not going to get any "JSP offers 5x better performance"-type killer arguments to win your case, because basically there aren't any. Both technologies are good enough at doing what they do. If client is asking for a Windows technology because they already have resources to support such a technology, then thats the argument that wins it. A windows client with a Java back end considerably increases the skill set required to support the app - that would be a factor.
 
Jeroen Wenting
Ranch Hand
Posts: 5093
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The main reason to use a JSP based frontend (don't use ONLY JSPs, use an MVC system with JSPs as the view component) is the lower deployment cost.

If the client only has a very few workstations that's not an issue, if he has a large number (possibly on geographically distant locations) it can save a lot of money as they don't have to worry about keeping the workstations updated with the latest version of the client software.
All this of course comes at the cost of needing more computation power in the server as you can't have the client do computations and send the data to the server ready for storage in the database (or whereever).

For many of our customers that's a selling argument over a thick client.
They already have the big servers as they're moving to a JSP based solution from a traditional terminal emulator.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There's also another option to alleviate the problem of managing a large number of client deployments -- use Java Web Start to deploy rich client applications (usually Swing but it should be possible to use SWT as well, for example) from the server.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!