skip to main | skip to sidebar

T

CGI vs Servlet

  • CGI:  Common Gateway Interface, creates a heavy weight process to handle each http request. N number of copies of the same traditional CGI programs is copied into memory to serve N number of requests.
  • Servlet: Spawns a lightweight Java thread to handle each http request. Single copy of a type of servlet but N number of threads (thread sizes can be configured in an application server). In MVC, servlets process requests and select JSP views. So servlets act as controller.
Newer Post Older Post Home

About Me

lucyjava
View my complete profile

Blog Archive

  • ▼  2007 (106)
    • ►  September (19)
    • ▼  July (42)
      • Servlet Config vs. Servlet Context
      • web structure
      • Servlet Reload
      • Life cycle of a servlet
      • Maintain state for stateless HTTP
      • CGI vs Servlet
      • web.xml
      • EJB classloader vs. WAR classloader
      • J2EE classloader
      • ejb_jar.xml
      • application.xml
      • Web Server vs. App Server
      • J2EE Design Patterns
      • Structure of ear file
      • how classes are found
      • jar shared by web and EJB modules
      • MVC 2
      • MVC
      • Key benefits of multitier J2EE
      • Multitier
      • advantage of multitier artchitecture
      • J2EE API
      • Protocols
      • J2EE server
      • J2EE container
      • component vs service
      • J2EE component
      • What is J2EE
      • Core Dump
      • Reasons to cause OutOfMemoryError
      • OutOfMemoryError
      • Key Points
      • Minimising memory leaks
      • Detect memory leaks
      • Performance Tips
      • Minimize the creation of objects
      • Performance
      • Call Web Server from Java
      • Socket
      • Singleton & Factory
      • Benefits of Factory Pattern
      • Factory Method/Abstract Factory
    • ►  June (45)