1. What is Virtual Server? Why it is used?

Answer:
On the Internet, a virtual server is a server (computer and various server programs) at someone else's location that is shared by multiple Web site owners so that each owner can use and administer it as though they had complete control of the server. Some Internet service providers (ISPs) offer a virtual server service instead of, or in addition to, virtual hosting. Using a virtual server, a company or individual with a Web site can not only have their own domain name and IP address, but can administer their own file directories, add e-mail accounts and address assignments, assign multiple domain names that resolve to a basic domain name without involvement from the ISP, manage their own logs and statistics analysis, and maintain passwords. Users of a virtual server, however, do not have to manage the hardware aspects of running a server and effectively share the cost of expensive line connections to the Internet. Actually, I use Virtual Server for many of the same tasks that you already described. 1. Servicing applications on older platforms 2. Regression test against older platforms 3. Compatibility test of present against older platforms 4. Functional/Stress test of current platform/applications I treat Virtual Machine as a quick way to get back to a certain OS or a certain saved state, which can be persisted/copied onto any other machine. Thus, my automation focuses on making save/restore of state as easy as possible. From what I understand of VMWare snapshot, I believe the only "issue" with what Virtual Server does is that the VM transitions into and out of a "Saved VM" state, and you cannot interact with the VM in the "saved" state. But this process is pretty quick and you can copy the state around, so I do not see any problems. Disk space is cheap, so I just keep multiple VHDs, each with a different OS and service pack level, and I have my own custom VHD save/restore mechanism so that users can quickly find, use, and also share their VHDs from a centralized bank of images. 2. Short note : Virtual server configuration(apache)

Answer:
3. Short note on Servlet(Servlet basics)

Answer:
A servlet is a Java programming language class used to extend the capabilities of servers that host applications accessed via a request-response programming model. Although servlets can respond to any type of request, they are commonly used to extend

the applications hosted by Web servers. For such applications, Java Servlet technology defines HTTP-specific servlet classes. The javax.servlet and javax.servlet.http packages provide interfaces and classes for writing servlets. All servlets must implement the Servlet interface, which defines life-cycle methods. When implementing a generic service, you can use or extend the
GenericServlet class provided with the Java Servlet API. The HttpServlet class provides methods, such as doGet and doPost, for handling HTTP-specific services.

A servlet is a small program that runs on a server. The term was coined in the context of the Java applet, a small program that is sent as a separate file along with a Web (HTML) page. Java applets, usually intended for running on a client, can result in such services as performing a calculation for a user or positioning an image based on user interaction. Some programs, often those that access databases based on user input, need to be on the server. Typically, these have been implemented using a Common Gateway Interface (CGI) application. However, with a Java running in the server, such programs can be implemented with the Java programming language. The advantage of a Java servlet on servers with lots of traffic is that they can execute more quickly than CGI applications. Rather than causing a separate program process to be created, each user request is invoked as a thread in a single daemon process, meaning that the amount of system overhead for each request is slight. Instead of a URL that designates the name of a CGI application (in a "cgi-bin" subdirectory), a request in a form on a Web HTML page that results in a Java servlet getting called would call a URL that looks like this:

4. Problems with Servlet.

Answer: Page 32 of JSP Book.

5. How can we configure IP in multiple subdomains?

Answer:
6. How can we configure multiple websites with multiple domain names in an apache server?

Answer:
7. Short note : Relative path, Absolute path

Answer:
Absolute Path: Absolute path is something that independent or free from any relationship. When we use absolute URL, we point directly to a file in internet. If two URL is identical, they points to the same file. Relative Path: Relative path points to a file/directory in relation to the present file/directory. Relative URLs are preferable for web maintenance. Relative URL are ***** than absolute URL.
8. Apache web server.

Answer:
9. How each individual of WAMP server work?

Answer:
10. Know about : Apache -> http.config MySQL -> mysql.ini PHP -> php.ini

Answer:

11. Short note on HTTP(HTTP basics)

Answer:
12. HTTP protocol.

Answer:
13. HTTP request/respond model.

Answer: Page 20 of JSP Book.

14. What is CGI? What are the most popular languages for CGI programming?

Answer:
15. What are the advantages of scripting languages over traditional CGI languages for server side programming?

Answer:
16. Client side VS. Server side programming OR short note: Server side programming & Client side programming (in relation to World Wide Web?)

Answer: Client side programming

Client side is the user end of the experience. As a developer we cant impose specific environment or browser client side, it is selected by user. In client side language user can use HTML, JavaScript.

Server side programming

Server side is based on server end.

We can decide which platforms, OS, programming languages, frameworks & libraries will be used. Any programming language can be used to implement various web applications in PHP, Python, Java etc. Client side scripting is possible to be Server side scripting cant be blocked by the blocked. user. Client side scripting has some limitation Server side scripting doesnt have any with browser. browser limitations.

Server Side Programming: Client Side Programming: 17. Short note : MVC(Model View Controller) -> just basic

Answer:
MVC was first described by Xerox in a number of papers published in the late 1980s. The key point of using MVC is to separate logic into three distinct units: the Model, the View, and the Controller.
 Model Business logic & data.  View Presentation logic.  Controller Request processing.

In a server application, we commonly classify the parts of the application as business logic, presentation, and request processing. Business logic is the term used for the manipulation of an application's data, such as customer, product, and order

information. Presentation refers to how the application data is displayed to the user, for example, position, font, and size. And finally, request processing is what ties the business logic and presentation parts together. In MVC terms, the Model corresponds to business logic and data, the View to the presentation, and the Controller to the request processing.
18. What you know about state management or Session Tracking Explained?

Answer:
Keeping track of which requests come from the same user isn't as easy as it may look. HTTP is a stateless, request-response protocol. What this means is that the browser sends a request for a web resource; the web server processes the request and returns a response. The server then forgets this transaction ever happened. So when the same browser sends a new request; the web server has no idea that this request is related to the previous one. This is fine as long as you're dealing with static files, but it's a problem in an interactive web application. There are two ways to solve this problem, and they have both been used extensively for web applications with a variety of server-side technologies. The server can either return all information related to the current user (the client state) with each response and let the browser send it back as part of the next request, or it can save the state somewhere on the server and send back only an identifier that the browser returns with the next request. The identifier is then used to locate the state information saved on the server. In both cases, the information can be sent to the browser in one of three ways:
 As a cookie  Embedded as hidden fields in an HTML form

 Encoded in the URLs in the response body, typically as links to other application pages (this is known as URL rewriting) Figure bellow outlines these methods.

Figure: Client state information transportation methods

A cookie is a name/value pair that the server passes to the browser in a response header. The browser stores the cookie for the time specified by the cookie's expiration time attribute. When the browser sends a request to a server, it checks its "cookie jar" and includes all cookies it has received from the same server (that has not yet expired) in the request headers. Cookies used for state management don't have an expiration time and expire as soon as the user closes the browser. Using cookies is the easiest way to deal with the state issue, but some browsers don't support cookies. In addition, a user may

disable cookies in a browser that does support them because of privacy concerns. Hence, we can't rely on cookies alone. If hidden fields in an HTML form are used to send the state information to the browser, the browser returns the information to the server as regular HTTP parameters when the form is submitted. When the state information is encoded in URLs, it's returned to the server as part of the request URL path, for instance when the user clicks on an encoded link. Sending all state information back and forth between the browser and server isn't efficient, so most modern server-side technologies keep the information on the server and pass only an identifier between the browser and the server. This is called session tracking; all requests from a browser that contains the same identifier (session ID) belong to the same session, and the server keeps track of all information associated with the session. JSP hides all details of cookie-based session tracking and supports the URL rewriting variety with a bit of help from the page author. In addition, the specification allows a container to use the session mechanism built into the Secure Socket Layer (SSL), the encryption technology used by HTTPS. SSL-based session tracking is currently not supported by any of the major servlet containers, but all of them support the cookie and URL rewriting techniques. No matter which mechanism is used, session data is always available to JSP pages through the session scope.2 Information saved in the session scope is available to all pages requested by the same browser during the lifetime of a session. A session starts when the browser makes the first request for a JSP page in a particular application. The application can explicitly end the session (for instance when the user logs out or completes a transaction), or the JSP container can end it after a period of user inactivity (the default value is typically 30 minutes after the last request). Note that there's no way for the server to tell if the user closes the browser, because there's no permanent connection between the browser and the server, and no message is sent to the server when the browser disappears. Still, closing the browser usually means losing the session ID; the cookie expires, or the encoded URLs are no longer available. So when the user opens a browser again, the server can't associate the new request with the previous session, and therefore creates a new session. However, all session data associated with the previous session remains on the server until the session times out.
19. Make connection between PHP to database.(just syntax)

Answer:
20. Syntax : str_replace() mysql_query() mysql_fetch_array()

mysql_fetch_object()

Answer:

21. GET & POST method.

Answer:
22. Output buffering. Why it is used? Where it is used?

Answer:
23. Short note : Server Variable

Answer:
24. Short note : Variable Ordering

Answer:
25. Short note: Environment variable Session variable Post variable Make the serial about which come first. Server configuration variable order.

Answer:
26. Directory Structure Tree.

Answer:
27. Short note : Domain(all about domain)

Answer:
28. Short note : Application Program Interface(API)

Answer:
29. From HTML :

Anchor Order list Listed item Table

Answer:

30. What are the advantages of Table based website design instead of Frame based design and vice-versa?

Answer:
31. What is mean by Internet merchant banking?

Answer:

32. What are the common mechanisms used for session tracking?

Answer:
Cookies SSL sessions URL- rewriting