This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
It's an old technique to keep the value of a variable between request. Let's think of an example. You enter your name in a text field, and then press the submit button. One way ot store the value is to put it in a hidden input field, in the next page, inside a form. <input type="hidden" name="username" value="Jothi"/> When you submit again to an other page, your name is sent back again. Your name will be available as long as it is stored in a hidden field. You can imagine that it is a pain to maintain.
Hi Vyas, welcome to the ranch. You may not be aware of the Javaranch Naming Policy yet. Could you please read it, and change your name accordingly ? Thank you. http://www.javaranch.com/name.jsp
Regardless, I could not understand the pain
With hidden variables, you would have to keep track of your variables through all pages, which is challenging when you have a lot of input elements. This was mainly used when session were not available in the old days