|
INTERVIEW QUESTIONS
ACCOUNTS
DETAILS
Question: What is the difference between an application server and a Web server?
Answer: A Taking a big step back, a Web server serves pages for viewing in a Web browser, while an application server provides methods that client applications can call. A little more precisely, you can say that:
A Web server exclusively handles HTTP requests, whereas an application server serves business logic to application programs through any number of protocols.
Let's examine each in more detail.
The Web server
A Web server handles the HTTP protocol. When the Web server receives an HTTP request, it responds with an HTTP response, such as sending back an HTML page. To process a request, a Web server may respond with a static HTML page or image, send a redirect, or delegate the dynamic response generation to some other program such as CGI scripts, JSPs (JavaServer Pages), servlets, ASPs (Active Server Pages), server-side JavaScripts, or some other server-side technology. Whatever their purpose, such server-side programs generate a response, most often in HTML, for viewing in aWeb browser.
Understand that a Web server's delegation model is fairly simple. When a request comes into the Web server, the Web server simply passes the request to the program best able to handle it. The Web server doesn't provide any functionality beyond simply providing an environment in which the server-side program can execute and pass back the generated responses. The server-side program usually provides for itself such functions as transaction processing, database connectivity, and messaging.
While a Web server may not itself support transactions or database connection pooling, it may employ various strategies for fault tolerance and scalability such as load balancing, caching, and clustering?features oftentimes erroneously assigned as features reserved only for application servers.
The application server
As for the application server, according to our definition, an application server exposes business logic to client applications through various protocols, possibly including HTTP. While a Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object (or a function in the procedural world).
Such application server clients can include GUIs (graphical user interface) running on a PC, a Web server, or even other application servers. The information traveling back and forth between an application server and its client is not restricted to simple display markup. Instead, the information is program logic. Since the logic takes the form of data and method calls and not static HTML, the client can employ the exposed business logic however it wants.
In most cases, the server exposes this business logic through a component API, such as the EJB (Enterprise JavaBean) component model found on J2EE (Java 2 Platform, Enterprise Edition) application servers. Moreover, theapplication server manages its own resources. Such gate-keeping duties include security, transaction processing, resource pooling, and messaging. Like aWeb server, an application server may also employ various scalability and fault-tolerance techniques.
An example
As an example, consider an online store that provides real-time pricing and availability information. Most likely, the site will provide a form with which you can choose a product. When you submit your query, the site performs a lookup and returns the results embedded within an HTML page. The site may implement this functionality in numerous ways. I'll show you one scenario that doesn't use anapplication server and another that does. Seeing how these scenarios differ will help you to see the application server's function.
Scenario 1: Web server without an application server
In the first scenario, a Web server alone provides the online store's functionality. The Web server takes your request, then passes it to a server-side program able to handle the request. The server-side program looks up the pricing information from a database or a flat file. Once retrieved, the server-side program uses the information to formulate the HTML response, then theWeb server sends it back to your Web browser.
To summarize, a Web server simply processes HTTP requests by responding with HTML pages.
Scenario 2: Web server with an application server
Scenario 2 resembles Scenario 1 in that the Web server still delegates the response generation to a script. However, you can now put the business logic for the pricing lookup onto an application server. With that change, instead of the script knowing how to look up the data and formulate a response, the script can simply callthe application server's lookup service. The script can then use the service's result when the script generates its HTML response.
In this scenario, the application server serves the business logic for looking up a product's pricing information. That functionality doesn't say anything about display or how the client must use the information. Instead, the client andapplication server send data back and forth. When a client calls the application server's lookup service, the service simply looks up the information and returns it to the client.
By separating the pricing logic from the HTML response-generating code, the pricing logic becomes far more reusable between applications. A second client, such as a cash register, could also call the same service as a clerk checks out a customer. In contrast, in Scenario 1 the pricing lookup service is not reusable because the information is embedded within the HTML page. To summarize, in Scenario 2's model, the Web server handles HTTP requests by replying with an HTML page while the application server serves application logic by processing pricing and availability requests.
Caveats
Recently, XML Web services have blurred the line between application servers and Web servers. By passing an XML payload to a Web server, the Web server can now process the data and respond much as application servers have in the past.
Additionally, most application servers also contain a Web server, meaning you can consider a Web server a subset of an application server. While application servers contain Web server functionality, developers rarely deploy application servers in that capacity. Instead, when needed, they often deploy standalone Web servers in tandem with application servers. Such a separation of functionality aids performance (simple Web requests won't impactapplication server performance), deployment configuration (dedicated Web servers, clustering, and so on), and allows for best-of-breed product selection.
Author Bio
Tony Sintes is an independent consultant and founder of First Class Consulting, a consulting firm that specializes in bridging disparate enterprise systems and training. Outside of First Class Consulting, Tony is an active freelance writer, as well as author of Sams Teach Yourself Object-Oriented Programming in 21 Days (Sams, 2001; ISBN: 0672321092).
Application server is a Web server with the notion of logic. In other words, you can host applications there and expose those applications through a Web-based product. Web servers just service up content, HTML pages and other Web-capable files.
|
|
|
Category |
Accounts Interview Questions & Answers -
Exam Mode /
Learning Mode
|
Rating |
(0.2) By 9046 users |
Added on |
8/6/2015 |
Views |
69932 |
Rate it! |
|
|
Question:
What is the difference between an application server and a Web server?
Answer:
A Taking a big step back, a Web server serves pages for viewing in a Web browser, while an application server provides methods that client applications can call. A little more precisely, you can say that:
A Web server exclusively handles HTTP requests, whereas an application server serves business logic to application programs through any number of protocols.
Let's examine each in more detail.
The Web server
A Web server handles the HTTP protocol. When the Web server receives an HTTP request, it responds with an HTTP response, such as sending back an HTML page. To process a request, a Web server may respond with a static HTML page or image, send a redirect, or delegate the dynamic response generation to some other program such as CGI scripts, JSPs (JavaServer Pages), servlets, ASPs (Active Server Pages), server-side JavaScripts, or some other server-side technology. Whatever their purpose, such server-side programs generate a response, most often in HTML, for viewing in aWeb browser.
Understand that a Web server's delegation model is fairly simple. When a request comes into the Web server, the Web server simply passes the request to the program best able to handle it. The Web server doesn't provide any functionality beyond simply providing an environment in which the server-side program can execute and pass back the generated responses. The server-side program usually provides for itself such functions as transaction processing, database connectivity, and messaging.
While a Web server may not itself support transactions or database connection pooling, it may employ various strategies for fault tolerance and scalability such as load balancing, caching, and clustering?features oftentimes erroneously assigned as features reserved only for application servers.
The application server
As for the application server, according to our definition, an application server exposes business logic to client applications through various protocols, possibly including HTTP. While a Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object (or a function in the procedural world).
Such application server clients can include GUIs (graphical user interface) running on a PC, a Web server, or even other application servers. The information traveling back and forth between an application server and its client is not restricted to simple display markup. Instead, the information is program logic. Since the logic takes the form of data and method calls and not static HTML, the client can employ the exposed business logic however it wants.
In most cases, the server exposes this business logic through a component API, such as the EJB (Enterprise JavaBean) component model found on J2EE (Java 2 Platform, Enterprise Edition) application servers. Moreover, theapplication server manages its own resources. Such gate-keeping duties include security, transaction processing, resource pooling, and messaging. Like aWeb server, an application server may also employ various scalability and fault-tolerance techniques.
An example
As an example, consider an online store that provides real-time pricing and availability information. Most likely, the site will provide a form with which you can choose a product. When you submit your query, the site performs a lookup and returns the results embedded within an HTML page. The site may implement this functionality in numerous ways. I'll show you one scenario that doesn't use anapplication server and another that does. Seeing how these scenarios differ will help you to see the application server's function.
Scenario 1: Web server without an application server
In the first scenario, a Web server alone provides the online store's functionality. The Web server takes your request, then passes it to a server-side program able to handle the request. The server-side program looks up the pricing information from a database or a flat file. Once retrieved, the server-side program uses the information to formulate the HTML response, then theWeb server sends it back to your Web browser.
To summarize, a Web server simply processes HTTP requests by responding with HTML pages.
Scenario 2: Web server with an application server
Scenario 2 resembles Scenario 1 in that the Web server still delegates the response generation to a script. However, you can now put the business logic for the pricing lookup onto an application server. With that change, instead of the script knowing how to look up the data and formulate a response, the script can simply callthe application server's lookup service. The script can then use the service's result when the script generates its HTML response.
In this scenario, the application server serves the business logic for looking up a product's pricing information. That functionality doesn't say anything about display or how the client must use the information. Instead, the client andapplication server send data back and forth. When a client calls the application server's lookup service, the service simply looks up the information and returns it to the client.
By separating the pricing logic from the HTML response-generating code, the pricing logic becomes far more reusable between applications. A second client, such as a cash register, could also call the same service as a clerk checks out a customer. In contrast, in Scenario 1 the pricing lookup service is not reusable because the information is embedded within the HTML page. To summarize, in Scenario 2's model, the Web server handles HTTP requests by replying with an HTML page while the application server serves application logic by processing pricing and availability requests.
Caveats
Recently, XML Web services have blurred the line between application servers and Web servers. By passing an XML payload to a Web server, the Web server can now process the data and respond much as application servers have in the past.
Additionally, most application servers also contain a Web server, meaning you can consider a Web server a subset of an application server. While application servers contain Web server functionality, developers rarely deploy application servers in that capacity. Instead, when needed, they often deploy standalone Web servers in tandem with application servers. Such a separation of functionality aids performance (simple Web requests won't impactapplication server performance), deployment configuration (dedicated Web servers, clustering, and so on), and allows for best-of-breed product selection.
Author Bio
Tony Sintes is an independent consultant and founder of First Class Consulting, a consulting firm that specializes in bridging disparate enterprise systems and training. Outside of First Class Consulting, Tony is an active freelance writer, as well as author of Sams Teach Yourself Object-Oriented Programming in 21 Days (Sams, 2001; ISBN: 0672321092).
Application server is a Web server with the notion of logic. In other words, you can host applications there and expose those applications through a Web-based product. Web servers just service up content, HTML pages and other Web-capable files. Source: CoolInterview.com
If you have the better answer, then send it to us. We will display your answer after the approval.
Rules to Post Answers in CoolInterview.com:-
- There should not be any Spelling Mistakes.
- There should not be any Gramatical Errors.
- Answers must not contain any bad words.
- Answers should not be the repeat of same answer, already approved.
- Answer should be complete in itself.
|
|
Related Questions |
View Answer |
|
What are respectively some remarkable functions of myosin, CD4, albumin, keratin, immunoglobulin, reverse transcriptase, hemoglobin, and insulin?
|
View Answer
|
|
serviceconf' can be used to control xinetd managed services. A. True B. False
|
View Answer
|
|
. What are the most typical functional units of the Client/Server applications?
|
View Answer
|
|
An 8-engine Adaptive Server is undergoing a high rate of Logical I/Os and spinlock contention in the default data cache. The DBA has used Sybase ASE Monitor and has found that two 4MB tables are table-scanning within the application. This is causing 50% of the server's Logical I/Os. The code within the application cannot be changed. The task for the DBA is to increase throughput of the Adaptive Server and lower the amount of spinlock contention without changing indexes, tables or the application. Which two are valid operations which should be done to meet this objective? (Choose 2.) A. Create two named caches of 2 MB each and then recycle the Adaptive Server to activate them. B. Create two named caches of 5 MB each and then recycle the Adaptive Server to activate them. C. Create two 5MB 16KB Page Pools within the default data cache. Bind the two small tables to these page pools. D. Bind the two tables to their own newly-created and active named cache. E. Compress the tables which join to the two small tables so that they are chosen as outer tables. This will eliminate the need to table scan the small tables.
|
View Answer
|
|
Given the following statement: create index idx1 on titles(title_id) on new_segment Where: The titles table has 3 partitions The target segment new_segment spans 10 devices The max parallel degree parameter is 25 If available worker processes at runtime is 5, what is the total number of producers used for the parallel sort? A. 10 B. 3 C. 25 D. 1
|
View Answer
|
|
A strong name consists of the assembly's identity its simple text name, version number, and culture information (if provided) plus a public key and a digital signature. It is generated from an assembly file (the file that contains the assembly manifest, which in turn contains the names and hashes of all the files that make up the assembly), using the corresponding private key. Assemblies with the same strong name are expected to be identical.
Strong names guarantee name uniqueness by relying on unique key pairs. No one can generate the same assembly name that you can, because an assembly generated with one private key has a different name than an assembly generated with another private key.
When you reference a strong-named assembly, you expect to get certain benefits, such as versioning and naming protection. If the strong-named assembly then references an assembly with a simple name, which does not have these benefits, you lose the benefits you would derive from using a strong-named assembly and revert to DLL conflicts. Therefore, strong-named assemblies can only reference other strong-named assemblies.
There are two ways to sign an assembly with a strong name:
1. Using the Assembly Linker (Al.exe) provided by the .NET Framework SDK. 2. Using assembly attributes to insert the strong name information in your code. You can use either the AssemblyKeyFileAttribute or the AssemblyKeyNameAttribute, depending
T
|
View Answer
|
|
ABO and rhesus (Rh) system, the second rhesus positive baby of a Rh negativemother is at a greater risk than the first
|
View Answer
|
|
The epidermal and dermal epithelia grow downwards along the suture track. Question Published at Wednesday, 01 July 2009 in Category Pathology. Question Visited: 368 Times.
Answer of Selected Question
Answer:
* Collapse/Expand Answer of Question The epidermal and dermal epithelia grow downwards along the suture track.
True
Do you have any collection of Interview Questions and interested to share with us!! Please send that collection to [email protected] along with the category and sub category information
* StumbleUpon * Digg * Delicious * Twitter * FaceBook * LinkedIn * Google * Yahoo * MySpace * Tell Your Friend
The epidermal and dermal epithelia grow downwards along the suture track.
Previous Interview Question Next Interview Question Monocytes clean the debris left by phagocytes. Fibroblasts have a contractile function, which helps to produce a small scar.
« previous123456789...3334next » Appropriate Answers of the selected Question [ The epidermal and dermal epithelia grow downwards along the suture track. ] from category Pathology...
Do you find this Answer incorrect or incomplete? Please e-mail us or place your comment or if you have correct answer then place in comment regarding this question "The epidermal and dermal epithelia grow downwards along the suture track." To ensure quality, each change is checked by our team, before it enters the main website database. If you desire so, the chang
|
View Answer
|
|
What is the difference of Cost Accounting and Financial Accounting?
|
View Answer
|
|
Does the accounting system appear to facilitate one specialty from financial, auditing, or cost managerial or tax accounting over the others?
|
View Answer
|
|
What are the effects of international accounting standards on accounting practices of developing nations?
|
View Answer
|
|
Where the financial accounting fails the cost accounting for is rescue but still there are some limitations deficiencies in the system?
|
View Answer
|
|
What is the difference between cost accounting management accounting and financial accounting?
|
View Answer
|
|
What is the relationship between cost accounting financial accounting and managerial accounting?
|
View Answer
|
|
Other accounting interview questions to expect when you interview for an accountancy job include:
|
View Answer
|
|
Other accounting interview questions to expect when you interview for an accountancy job include:
|
View Answer
|
|
What do you consider to be the biggest challenge facing the accounting profession today?
|
View Answer
|
|
Describe any accounting process that you have developed or revised.
|
View Answer
|
|
Give me examples of the accounting reports you have prepared.
|
View Answer
|
|
You are creating a high level class diagram for your solution. You need to add one or more business entities to the diagram. Which entity or entities should you add? (Choose all that apply) A. Task time B. Pop-up window C. Project D. Lawyer E. Client F. Task description G. Time entry
|
View Answer
|
Please Note: We keep on updating better answers to this site. In case you are looking for Jobs, Pls Click Here Vyoms.com - Best Freshers & Experienced Jobs Website.
View All Accounts Interview Questions & Answers - Exam Mode /
Learning Mode
|