• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Performance Guidelines on JSP vs. XML/HTML usage

 
Ranch Hand
Posts: 1157
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Could we discuss some guidelines to determine when we should use JSP solution vs. XML/HTML solution from a performance point of view.Also can we elaborate on the possible pitfalls?
In the first place, I assume the above technologies are not alternate technologies and has to co-exist with each other.
Thanks in advance,
Sandeep Desai
vgdesai@bom3.vsnl.net.in

  1. Sun Certified Java Programmer Scored 93 per cent
  2. Oracle JDeveloper Rel. 3.0 - Develop Database Applications with Java Scored 56 out of 59
  3. IBM Enterprise Connectivity with J2EE Scored 72 per cent
  4. Enterprise Development on the Oracle Internet Platform Scored 44 out of 56

  5. [This message has been edited by Desai Sandeep (edited April 27, 2001).]
 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
An article related to this is "Savor success with Java on the front end" by Alex Kalinovsky at http://www.javaworld.com/javaworld/jw-04-2001/jw-0420-swing_p.html .
In this article, Alex points out two performance issues plaguing XML applications today -- lack of tools for code generation (especially for stylesheets) and processing (parsing) speed. He ends the article with a section on "basic rules of thumb" for when to use HTML/JSP versus Java Swing versus XML/XSLT. I think the WebCream product he mentions is interesting -- it converts Java (AWT or Swing) into HTML dynamically.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic