recommend book⇒Core Web Programming, Second Edition
		paperback
	ISBN10:	0-13-089793-0
	ISBN13:	978-0-13-089793-0
	publisher:	Prentice Hall
	published:	2001-06-03
	by:	Marty Hall and Gary Cornell
1250 pages. This is a great doorstop of a book. It has a few chapters on client-server programming in Java, and a section of that is on CGI. I have looked at hundreds of Java books and found nothing that deals in depth with client side Java talking to CGI, except Marty’s book. It is really very simple and he does an excellent job of explaining it. Marty has posted all the source code examples from the book for anyone to use. These contain updates and errata fixes you don’t get on the CD-ROM that comes with the book.
amazon.ca amazon.com chapters.indigo.ca powells.com amazon.fr barnesandnoble.com amazon.de amazon.co.uk

	recommend book⇒Core Servlets and Java Server Pages
		paperback
	ISBN10:	0-13-089340-4
	ISBN13:	978-0-13-089340-6
	publisher:	Prentice Hall
	published:	2000-05-26
	by:	Marty Hall
Complete text of the book available on line in pdf format.
amazon.ca amazon.com chapters.indigo.ca powells.com amazon.fr barnesandnoble.com amazon.de amazon.co.uk

	recommend book⇒Core Servlets and Java Server Pages
		paperback
	ISBN10:	0-13-067614-4
	ISBN13:	978-0-13-067614-6
	publisher:	Pearson Education
	published:	2001-12-26
	by:	Marty Hall
Complete text of the book available on line in pdf format.
amazon.ca amazon.com chapters.indigo.ca powells.com amazon.fr barnesandnoble.com amazon.de amazon.co.uk

GET and POST are two ways to request information from a server. In GET all the request information is contained tacked onto the URL (which can thus be made part of a bookmark). In PUT it is contained in a separate trailing message. GET is idempotent, a mathematician’s word meaning "gives identical results with identical input and has no side effects". Thus if you do a second identical GET, the results can be fished out of cache, without reprocessing the request. In contrast, a POST is assumed to have side effects, or to produce different results each time it is invoked. It has some lasting effect on the world, e.g. submitting a membership application. The request has to be reprocessed from scratch.

The Cyberspyder people make a free tool to help you understand what browsers and servers send back and forth to each other called Webbug. It lets you compose GET commands and see the results. Unfortunately, it does not let you snoop on what browsers and servers are sending to each other.

Forms

• The actionscript comes from the <form method="POST" action="actionscript"> It it the name of the program that will handle the request on the server.
• The referrer is the URL of the page containing the form.
• The Content-Length is the length in bytes of the parm=value list following the blank line.
• The data are encoded as parm=value&parm=value. The parm names and values are url-encoded with java.util.net.URLEncoder.encode, which converts spaces to +, and special characters to %xx where xx is the hex equivalent. Note that even POST can’t send raw binary data. It must be URL encoded. The = and & are not URL encoded, just the parameter names and their values.
• The submit button has a hidden name and value as well so the server can tell which submit button was pressed.
• Multiple select fields (where you are allowed to select any combination of choices) are sent like this &Currency=CAD&Currency=USD&Currency=EUR

When you use the GET protcol the parameters are tacked on the end of the URL, separated-by a ?.

Beware of using raw Sockets for get and put for long messages. Responses come in blocks with a length field on the front. You have to bypass these. They will show up as something like 2000 cr lf in the middle of your data.

POST and GET are not efficient ways for transmitting large volumes of binary data. For that you would set up a separate socket connection.