• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

About SingleThreadModel

 
Fisher Daniel
Ranch Hand
Posts: 582
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear all,
I am reading Java Servlet Specification v2.4 Proposed Final Draft version2.
It says that SingleThreadModel will be depreceted( Section 2.2.1, Section 2.3.3.1, Section 14.2.24).
But the objective 7.3 of SCWCD (Identify the interface used to declare that a servlet must use the single thread model)
If its document will be final draft, What will Sun Microsystem, Inc. will do? Changes that objective or changes the version of SCWCD about Servlet?
thanks
daniel
 
Axel Janssen
Ranch Hand
Posts: 2166
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Daniel: The current test is about Servlet 2.3.
There are rumours that the exam will be upgrated with J2EE1.4 (with Servlet2.4 and JSP2.0). But this will take some time.
SingleThreadModel do have serious negative performance implications. It isn't used in praxis.
Why do they make you learn stuff which will be deprecated in short time?
SingleThreadModel is the oposite of "normal" servlet behaviour: one servlet instance servicing all requests. Understanding SingleThreadModel helped me to understand "normal" servlet behaviour.
[ March 10, 2003: Message edited by: Axel Janssen ]
 
Jessica Sant
Sheriff
Posts: 4313
Android IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Axel Janssen:
SingleThreadModel is the oposite of "normal" servlet behaviour: one servlet instance servicing all requests. Understanding SingleThreadModel helped me to understand "normal" servlet behaviour.

yes -- it also helps you realize the ramifications of a distributed system... using instance variables and how that can be affected by multiple threads etc.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic