servlet是当网站用户从服务器请求URL时运行某些功能的Java类。这些函数可以完成将数据保存到数据库、执行逻辑和返回加载页面所需的信息(如JSON数据)等任务。

大多数Java程序使用main()方法在程序运行时执行代码。Java servlet包含doGet()和doPost()方法，它们的作用与main()方法类似。当用户向映射到该servlet的URL发出GET或POST请求时，将执行这些函数。因此，用户可以为GET请求加载页面，或者存储来自POST请求的数据。

当用户发送GET或POST请求时，服务器读取目录中每个servlet类顶部的@WebServlet，以决定调用哪个servlet类。例如，假设你有一个ChatBox类，顶部是这样的:

@WebServlet("/chat")
public class ChatBox extends HttpServlet {

当用户请求/chat URL时，ChatBox类将被执行。

您刚刚得到了一个正常servlet的答案。但是，我想与您分享一些关于Servlet 3.0的内容

What is first a Servlet? A servlet is a Web component that is managed by a container and generates dynamic content. Servlets are Java classes that are compiled to byte code that can be loaded dynamically into and run by a Java technology-enabled Web server or Servlet container. Servlet 3.0 is an update to the existing Servlet 2.5 specification. Servlet 3.0 required API of the Java Platform, Enterprise Edition 6. Servlet 3.0 is focussed on extensibility and web framework pluggability. Servlet 3.0 bring you up some extensions such as Ease of Development (EoD), Pluggability, Async Support and Security Enhancements Ease of Development You can declare Servlets, Filter, Listeners, Init Params, and almost everything can be configured by using annotations Pluggability You can create a sub-project or a module with a web-fragment.xml. It means that it allows to implement pluggable functional requirements independently. Async Support Servlet 3.0 provides the ability of asynchronous processing, for example: Waiting for a resource to become available, Generating response asynchronously. Security Enhancements Support for the authenticate, login and logout servlet security methods

我从Java Servlet教程中找到的

servlet只是一个响应特定类型网络请求的类——最常见的是HTTP请求。基本上，servlet通常用于实现web应用程序——但也有各种框架在servlet之上运行(例如Struts)，以提供比servlet提供的“这是一个HTTP请求，写入此HTTP响应”级别更高级别的抽象。

servlet运行在处理网络端(例如解析HTTP请求，连接处理等)的servlet容器中。Tomcat是最著名的开源servlet容器之一。

Servlet是web应用程序中用来创建动态网页的服务器端技术。servlet实际上是一个api，它由一组类和接口组成，具有一定的功能。当我们使用Servlet API时，我们可以使用Servlet类和接口的预定义功能。

Servlet的生命周期:

Web容器维护servlet实例的生命周期。

1。加载Servlet类

２ ． 创建Servlet实例

3.Init()方法被调用

4所示。调用Service()方法

５ ． 调用Destroy()方法

当客户端(浏览器)提出请求时，web-container检查servlet是否正在运行，如果是，则调用service()方法并向浏览器提供响应。

当servlet没有运行时，web-container遵循以下步骤。

1. Classloader装入servlet类

2. 实例化servlet

3.初始化servlet

4.调用service()方法

服务请求后，web-container等待特定的时间，在这段时间内，如果请求来了，那么它只调用service()方法，否则它调用destroy()方法。

什么是Servlet?

A servlet is simply a class which responds to a particular type of network request - most commonly an HTTP request. Basically servlets are usually used to implement web applications - but there are also various frameworks which operate on top of servlets (e.g. Struts) to give a higher-level abstraction than the "here's an HTTP request, write to this HTTP response" level which servlets provide. Servlets run in a servlet container which handles the networking side (e.g. parsing an HTTP request, connection handling etc). One of the best-known open source servlet containers is Tomcat. In a request/response paradigm, a web server can serve only static pages to the client To serve dynamic pages, a we require Servlets. Servlet is nothing but a Java program This Java program doesn’t have a main method. It only has some callback methods. How does the web server communicate to the servlet? Via container or Servlet engine. Servlet lives and dies within a web container. Web container is responsible for invoking methods in a servlets. It knows what callback methods the Servlet has.

请求流程

Client sends HTTP request to Web server Web server forwards that HTTP request to web container. Since Servlet can not understand HTTP, its a Java program, it only understands objects, so web container converts that request into valid request object Web container spins a thread for each request All the business logic goes inside doGet() or doPost() callback methods inside the servlets Servlet builds a Java response object and sends it to the container. It converts that to HTTP response again to send it to the client

容器如何知道哪个Servlet客户端请求了?

有一个文件叫web。xml 这是web容器的主文件 在这个文件中有关于servlet的信息- servlet Servlet-name servlet类 servlet-mappings-类似/Login或/Notifications的路径映射在这里 Servlet-name url模式 等等 web应用程序中的每个servlet都应该在这个文件中有一个条目 查找的方式是- url-pattern -> servlet-name -> servlet-class

如何“安装”servlet ? servlet对象继承自javax.servlet库。*。Tomcat和Spring可以用来利用这些对象来适应用例。

参考-在1.5x上观看- https://www.youtube.com/watch?v=tkFRGdUgCsE。这有一个很棒的解释。

除了以上，只是要指出流血的明显……

To many this is hyper obvious, but to someone used to writing apps which are just run and then end: a servlet spends most of its time hanging around doing nothing... waiting to be sent something, a request, and then responding to it. For this reason a servlet has a lifetime: it is initalised and then waits around, responding to anything thrown at it, and is then destroyed. Which implies that it has to be created (and later destroyed) by something else (a framework), that it runs in its own thread or process, and that it does nothing unless asked to. And also that, by some means or other, a mechanism must be implemented whereby this "entity" can "listen" for requests.

我建议阅读有关线程、进程和套接字的内容可以让你对此有所了解:这与一个基本的“hello world”应用程序的功能方式是完全不同的。

有人可能会说，术语“服务器”或“servlet”有点大材小用。一个更合理、更简单的名字可能是“responder”。选择术语“服务器”的原因是历史的:第一个这样的安排是“文件服务器”，多个用户/客户端终端将从中央机器请求特定的文件，然后该文件将像一本书或一盘炸鱼和薯条一样被“提供”。