Wordpress or Blogger?

Blogger	WordPress
It is Free and Easy to Use.	It is CMS (Content Management System).
It is Product of Google. Some of its parts are not Editable.	It is Free and Open Source. Everything can be editable if you have proper knowledge.
It has “Bullet Proof” Security to access the Data of Blog. No one can edit the Blog without proper authority.	It has Lower Security than Blogger.
No Need to Pay money for Hosting. Google provides hosting facility with Blogspot domain.	Need your own web hosting for hosting WordPress.
No need to pay for Giving Custom redirection to custom domain.	Need to pay money if you are using premium hosting service for redirection of domain.
It has limited Resources (plugins) and Themes.	Having Extra Plugin and Themes for each work like Social Media Bookmarks, Labels, Searches, etc…
We can’t sell the Blog to another party. Google doesn’t allow this type of Functionality services in its Privacy and Business Policy.	We can Sell the WordPress site to anyone. There is no Rule on selling and Purchasing.
Blogger can be used for most of the Posting purpose. Just for giving or sharing knowledge of you to others.	WordPress is used in Most of Websites today either they are knowledge sharing or business purpose.

 

PLEASE SHARE

Tweet

Read More

Servlet Life Cycle

Servlet Life Cycle With Diagram And Description

Servlet Life Cycle Methods

• init( )
• Service( )
• doGet( )
• doPost( )
• doXxx( )
• destroy( )

When the servlet is first created, its init() method is invoked, so init() is where you put one-time setup code. After this, each user request results in a thread that calls the service() method of the previously created instance. Multiple concurrent requests normally result in multiple threads calling service simultaneously, although your servlet can implement a special interface (SingleThreadModel) that stipulates that only a single thread is permitted to run at any one time. The service method then calls doGet(), doPost(), or another doXxx() method, depending on the type of HTTP request it received. Finally, if the server decides to unload a servlet, it first calls the servlet's destroy method.

PLEASE SHARE

Tweet

Read More

HTTP Request Headers I (Headers only)

Headers:

1.      Accept:-

-          This header specifies the MIME types that the browser or other clients can handle.

-          A servlet that can return a resource in more than one format can examine the Accept header to decide which format to use.

Ex - request.getHeader ("Accept");

2.      Accept- Charest:-

-          This header indicates the character sets the browser can use.

Ex - request.getHeader ("Accept-Charest");

3.      Authorization:- 

 

-          This header is used by clients to identify themselves when accessing password-protected Web pages.

4.      Connection:- 

-          This header indicates whether the client can handle persistent HTTP connections. Persistent connections permit the client or other browser to retrieve multiple files with a single socket Connection.

5.      Cookie:-

-          This header returns cookies to servers that previously sent them to the browser.

Ex- request.getHeader ("Accept-Charest");

6.      Host:-

-          This header indicates the host and port as given in the original URL.

Ex- request.getHeader ("Host");

7.      Referer:-

-       This header indicates the URL of the referring Web page.

Ex- request.getHeader ("Referer");

8.      Accept-Language:-

-          This header specifies the client's preferred languages in case the servlet can produce results in more than one language.

-          The value of the header should be one of the standard language codes such as en, en-us, da, etc.

9.      If-Modified-Since:-

-          This header indicates that the client wants the page only if it has been changed after the specified date.

-          The server sends a 304 (Not Modified) header if no newer result is available.

Ex- request.getHeader ("If-Modified-Since");

10.  If-Unmodified-Since:-

-          This header is the reverse of If-Modified-Since it specifies that the operation should succeed only if the document is older than the specified date.

Ex- request.getHeader ("If-Unmodified-Since");

11.  User-Agent:-

-          This header identifies the browser or other client making the request and can be used to return different content to different types of browsers.

-          However, the User-Agent header is quite useful for distinguishing among different categories of client.

-          For example, Japanese developers might see whether the User-Agent is an Imode cell phone, a Skynet cell phone, or a Web browser.

Ex- request.getHeader ("User-Agent");

12.  Accept-Encoding:-

-          Using an encoding the browser doesn't understand results in incomprehensible pages. 

-          Consequently, it is critical that you explicitly check the Accept-Encoding header before using any type of content encoding. 

-     Values of gzip or compress are the two most common possibilities.

13.  Content-Length:-

-          This header is applicable only to POST requests and gives the size of the POST data in bytes.

Ex- request.GetIntHeader ("Content-Length");

PLEASE SHARE

Tweet

Read More