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

a few interview questions

 
manish ahuja
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi

1)What's a better approach for enabling thread-safe servlets and JSPs? SingleThreadModel Interface or Synchronization? Should I use the SingleThreadModel interface or provide explicit synchronization to make my JSP pages and servlets thread safe?

2) Is there a way I can set my servlets to do thread pooling? Can I spawn a background thread from my servlet?
3) When building web applications, what are some areas where synchronization problems arrise?
Rgrds
 
Harsha Huddar
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1) Synchronisation is better as implementing SingleThreadModel is not fully thread safe.(Multiple threads can still access static variables)
SingleThreadModel is deprecated in Servlet2.4 spec and you are suggested to stop using this interface.
 
danny liu
Ranch Hand
Posts: 185
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
3)
a. Class variable
b. instance variable
c. session data
d. application data
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic