Posts

Showing posts from December, 2007
Java Final, Finally and Finalize Final: A method or variable that can't be overridden Finally: A block of code added after try / catch block. This block is guarnteed to execute even if due to a problem method returns from the catch block Finalize: a method which is your destructor method - code that's run to clean up objects that are no longer required. For example, objects which are memory cached would be flushed back to the disc in your finalize. (There is no guarantee that this will run or "when" will it call the garbage collector)
Well-known and less-known HTTP Request Methods (source wikipedia and www) HEAD (less-known) Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. Lots of bookmark management plugins use it for checking if the url still exists or not. GET (well-known) Requests a representation of the specified resource. By far the most common method used on the Web today. Should not be used for operations that cause side-effects (using it for actions in web applications is a common misuse). Idempotent ... See 'safe methods' below. POST (well-known Submits data to be processed (e.g. from an HTML form) to the identified resource. The data is included in the body of the request. This may result in the creation of a new resource or the updates of existing resources or both. PUT (less known) Uploads a repre