|
|
|
 |
| Home » Software Developments » Client/Server Applications |
| |
 |
Client/Server Applications |
|
| |
A client-server application describes two applications that work together on a (client)request/(server)response basis. The client requests an action or service from the service provider, which is the server. For example, to view this article you had to open up a (client) web browser, type in a URL and send it off to a web server. The web server processed and then returned the (HTML, PHP or ASP) page to your web browser, which then parses the data and displays it in your browser.
This is what is called a client server application. When you send or retrieve your email messages, you use the client-server architecture, in the sense that you use a client, like Outlook, to connect to a mail server somewhere to retrieve your messages. So it is an extremely vital architecture, without which remote data access would not exist. |
| |
| Client/Server Applications Made Easy - Client and Server Applications |
| |
| The Client Application |
So how does a client work? As I have stated before, the client basically makes requests to a server and then waits for a response, which it then interprets and displays. Now, how does the client know where the server is located? Well, for a client to connect to a server, it needs two things, the IP address and the port number.
The IP address tells the client where the server is located. A server can be located on the same machine, on a local network, or on the Internet. In other words, it could be located anywhere on the planet. Wherever the server is running, it will have an IP address and that is the only way a client can ID and connect to a server. As for the port number, that is where the server "listens" for connections. A port number is what the server uses to send and receive messages. |
| |
| The Server Application |
The server processes request made by a client and responds to the client. That is the core function of any server. Servers are generally passive as they wait for a client request.
Unlike clients, servers must run continually because a client can send a request at any time. Clients, on the other hand, don't have to run continually. They only need to be running when they require a service.
Many server applications allow for multiple clients to request a service. For example, while you are reading this page, others interested in this article could also request and read the same web page. |
| |
| |
|
Our Service Include |
|
| |
 Client Server Applications |
ASP.NET Applications |
Custom Software Development |
| |
Distributed Applications |
ERP Solutions |
Offshore Software Development |
| |
Desktop Applications |
Embedded Application |
Application Development |
| |
XML Applications |
E-Commerce Application |
Content Management System |
| |
SQL Server Applications |
M-Commerce Application |
OS Commerce Application |
| |
Oracle Applications |
|
|
|
| |
|
| |
| |
|
|
| |
| |
|
Software |
|
| |
 |
Client Server Applications |
|
| |
|
Distributed Applications |
|
| |
|
Desktop Applications |
|
| |
|
Oracle Applications |
|
| |
|
SQL Server Applications |
|
| |
|
ASP.NET Applications |
|
| |
|
Embedded Application |
|
| |
|
E-Commerce Application |
|
| |
|
OS Commerce Application |
|
| |
|
XML Applications |
|
| |
|
ERP Solutions |
|
|
| |
|
| |
|
Our Clients |
|
|
|
|
|
|
 |
|
 |
|
|
|
| |
|
| |
|
| |
| Copyright © 2006-2008 Yen Exall Soft. All Rights Reserved. Privacy | Disclaimer |
Web Development, Website designing, Software development, Web Hosting, ERP, E-Commerce, Multimedia, Desktop Applications, Client Server Application , Client Server Applications , ASP.NET Applications, Custom Software Development , Distributed Applications , ERP Solutions , Offshore Software Development , Content Management System, Desktop Applications, Embedded Application, Application Development , XML Applications , E-Commerce Application , Content Management System , SQL Server Applications , M-Commerce Application , OS Commerce Application, Oracle Applications
|
|
