Generic Servlet is protocol independent(i.e)it can handle all types of protocols like http, ftp, smtp etc.
GenericServlet class is direct subclass of Servlet Interface.
GenericServlet is an abstract class which implements Servlet, ServletConfig and java.io.Serializableinterfaces.
GenericServlet belongs to javax.servlet package.
HttpServlet is protocol dependent. It supports only http protocol.
HttpServlet class is the direct subclass of Generic Servlet.
HttpServlet is an abstract class which extends GenericServlet and implements java.io.Serializable interface.
HttpServlet belongs to javax.servlet.http package.
HttpServletResponse, are interfaces telling you what methods are available to call to do the things you need. In the normal course of working with Filters, Servlets, et al., you'll use HttpServletResponse often to tell your app how to respond to requests.
is one particular implementation of HttpServletResponse which gives you a convenient way to wrap an existing response with some logic of your own without having to write a whole new implementation of the interface. It has a lot of methods, so this is really nice
1. Http. Servlets are actually generic components designed to support any sort of operation that operates in a request/response cycle. That mostly means HTTP, but ages ago, IBM mainframes routinely did their online apps in a framework known as CICS (Customer Information Control System). It didn't use tcp/ip (not invented yet), and it didn't use HTML or HTTP (also not invented yet), but it was (mostly) request/response. So had servlets - or Java - existed back then, they would have been appropriate.
What an HttpServlet adds to the core servlet class is support for things specific to HTTP. For example, how URLs are processed, the difference between request types (GET, POST, HEAD, DELETE and so forth).
2. Both (an HttpServletRequest is a subclass of ServletRequest). When an HTTP client sends an HTTP(S) URL request to a J2EE webapp server, the server digests the incoming request and constructs an HttpServletRequest and corresponding HttpServletResponse object. Among other things, such as matching up sessions, if applicable.
Don't forget that all of the above are Interfaces, not classes, so the server's specific implementation class will implement the interface, but its properties and behaviours above and beyond what those interfaces demand are server-specific.
httpservletresponse is response of server
httpresponse is also the same I think so
Here is your answer
I hope this helped you so plz rate the answer
Servlet is html in java whereas JSP is java in html. Servlets run faster compared to JSP. ... JSP is a webpage scripting language that can generate dynamic content while Servlets are Java programs that are already compiled which also creates dynamic web content. In MVC, jsp acts as a view and servlet acts as a controller.
ServletContext is a configuration Object which is created when web application is started. It contains different initialization parameter that can be configured in web.xml.
ab ye pic dikhake ky show krna chahte
happen when the light gets bent it should be easy to figure out
mark as brilliant answer