All Apple fans, followers and especially its close Java community associates would have definitely been disturbed and shocked by Apple’s recent announcement that it would deprecate and denounce the including of the Java runtime in its Mac OS X. It was almost as though Apple was warning developers of the fact that Java would henceforth not be entailed in future versions of the Mac OS X; and by this there hovered a depressed and uncertain cloud over Java’s future associations with Apple’s Mac.
Earlier, we’ve introduced you to Java Servlets — what they are, life cycle, advantages. Let’s move ahead with Java Servlets and get some simple code to handle the HTTP GET Request to show you how to write a servlet.
Servlets can be used for handling both the GET Requests and the POST Requests. However in this post, let’s write the code for handling the GET Request. The HttpServlet class is used for handling HTTP GET Requests as it has some specialized methods that can efficiently handle the HTTP requests. These methods are;
An individual developing servlets for handling HTTP Requests needs to override one of these methods in order to process the request and generate a response. The servlet is invoked dynamically when an end-user submits a form.
We’ve been talking a lot about Linux lately. Let’s break out a bit from that and talk about another topic — the Java Servlet Technology. We’ll try to cover some basic aspects of Java Servlet Technology and may be a little more.
To give you a basic idea, Servlets are the server side components that are the Java counterpart to dynamic web content technologies like CGI, PHP and ASP.NET.
A lot of techniques have been developed to overcome the problems associated with Common Gateway Interface (CGI) and Servlets lie among them. Now, if you’re unsure of the problems associated with CGI then you need to move back to the early days of the Web. In the early days of Web, a server could construct a page dynamically but a separate process was required to handle each request, separate processes were required to read the data from the HTTP request and to write the data to the HTTP response, separate processes were required to communicate with the database. All these activities required a lot of server resources and hence, resulted in the development of programs that were not able to deliver the expected performance.
This is a reader submited article.
The Indian Developer Summit 2008 Features Co-located Conferences on Bleeding-edge .NET, Rich Web, Daring Java. The Call for Proposals are now Open and Nominations are invited for the Awards.
Under the hood of robust enterprise IT systems, infrastructure, software, products and applications, is the wisdom, passion, grit and experience of people who have contributed in multiple ways to make the end product successful. This collective ecosystem of “Developers” — decision makers, analysts, architects, engineers, project managers, designers, and programmers — is what makes the world of software tick.
The 2008 edition of the annual Great Indian Developer Summit, centered around the theme of “Recipes for Enterprise Productivity”, features a blockbuster convergence of three on-the-radar co-located conferences that no entity in the “Developer ecosystem” can ignore in their quest for success at work and in their careers — Bleeding-edge .NET, Rich Web and Daring Java.
I thought Flash Bashing, these days, are done only by the Internet’s semi-literates! Coming from a respectable person like James Gosling, the creator of Java is rather uncalled for. Nonetheless, it is understandable since his works somewhat relates him to JavaFX (supposedly, a competitor to the client side apps of the Flash Platform). He has all the rights to be on the defensive (rather abusive) perspective towards their extremely successful competitor – Flash.