Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Question on core concepts of servlets/jsp

 
Mikhail Jennings
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I wanted to know how to design servlets/jsp based web applications to handle many users.
What I am looking for is resources where I can learn the basics and advanced know-how of multithreaded servlet apps and how to code and design them.


thanks
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64633
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Pretty simple really:
  • Write your servlets to be thread-safe. This primarily means avoid instance and read-write static variables.
  • Be mindful of of simultaneous read-write access to session and application scoped variables.
  • Write JSPs using modern standards (no Java code in them) and they pretty much take care of themselves.


  • There are nuances, but that'll get you 99.5% there.
     
    Malatesh Karabisti
    Ranch Hand
    Posts: 153
    Java Oracle
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Dude seems like you are just starting with your Servlet/Jsp. my advice is don't directly jump to Design of your application. Try some "Hello world" application you will get good hold of basics.
     
    Ben Souther
    Sheriff
    Posts: 13411
    Firefox Browser Redhat VI Editor
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    +1 to both of the previous responses.

    Just to reiterate, the servlet spec was designed from day one with to be multi-user / multi-threaded so, as long as you avoid some of the common issues (primarily the use of instance or non-final static variables) your app -- at least the front end-- will automatically be multi-user. If you're app works with a shared resource such as a relational database, then you'll have to consider what could happen if two people try to access it at the same time.

    Like Malatesh said, have fun with some simple stuff first.
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic