• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

About SingleThreadModei Interface

 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear ALL,

can you tell me the main purpuse of SingleThreadModel Interface.
i think so it was deprecated from servlet 2.3 version
till yet there is no alterenative for SingleThreadModel Interface i mean to say upto servlet 2.5 v right?

i want to know that what is the main puropuse of SingleThreadModel Interface. why it was deprecated from servlet 2.3 version


regards
chandra SCJP5.0 97%
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The STM interface was meant to make servlets thread-safe by making sure that no two threads ran the same servlet instance at the same time. But over time it became clear that this is not sufficient to make web apps thread-safe; there are other concurrency issues (having to do with sessions and context attributes). So it was decided to abandon this nonfunctional approach to thread safety. The burden to make web apps thread-safe now lies solely with the application developer.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic