Delphi-Kylix
  Home arrow Delphi-Kylix arrow Page 3 - Client/Server Applications Made Easy
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Moblin 
JMSL Numerical Library 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
DELPHI-KYLIX

Client/Server Applications Made Easy
By: Leidago
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 3
    2006-12-04

    Table of Contents:
  • Client/Server Applications Made Easy
  • Client and Server Applications
  • Logical Addressing and Name Resolution
  • Error and Flow Control

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Client/Server Applications Made Easy - Logical Addressing and Name Resolution


    (Page 3 of 4 )

    Logical Addressing

    To be able to communicate with other computers on a network, a computer needs to be identifiable. Every computer on the network will have its own network adapter that has a unique and permanent physical address. This is what makes each computer identifiable. This address is also used to deliver data to a particular computer. This means that a computer's network adapter has to listen to every single transmission to determine if a particular message is addressed to its physical address.

    You can imagine that if you have twenty computers or more, your network will be very slow and inefficient at delivering messages. To reduce network traffic, administrators divide them into smaller networks (called subnets) and then set a hierarchical design so that a message can travel more efficiently to its destination.

    TCP/IP provides this subnetting capability through logical addressing. In TCP/IP, a computer's logical address is called an IP address. An IP address is a number used to identify and locate a computer on a network. Now, how is all of this relevant to client/server applications? It's quite straightforward really; for the client application to talk to a server application, it needs to know where the server application is located, and the only way to establish a connection with a server is through its IP address or host name.

    Name Resolution

    As we have established before, for the network to identify each computer in its domain, the computers will have network adapters that have unique prefabricated physical addresses, and TCP/IP uses IP addresses to identify a computer on a network. Both of these addressing schemes are numerical and somewhat difficult to remember; they're designed for convenience of the computer (which is very good with numbers), rather than for humans.

    For the average person it would be difficult to remember a computer's address is 192.168.0.1 or 131.121.134.146. TCP/IP therefore provides a parallel, user- oriented structure called domain names or DNS names. These names are alphanumeric in nature and easier to remember.

    This mapping of IP addresses to domain names is called name resolution. A group of computers called name servers store tables showing how to translate these domain names to and from IP addresses. Email and WWW addresses are expressed as DNS names, for example www.google.com or www.myname.com. Name service systems provide domain name/IP address mappings for DNS registered computers on the network. This ensures that you do not have to enter the IP address of a website to access it.

    The most common name resolution method used on the Internet is DNS, but there are others such as Windows Internet Name Services or WINS, which resolves Microsoft Windows NetBios names to IP addresses. How does this relate to the client server application? It provides us with another method of identifying the server location and name. Instead of entering the IP address to access the services provided by a server, we can now enter the domain name, which is easy to remember.

    More Delphi-Kylix Articles
    More By Leidago


       · This article shows you how to built client / server application in Delphi.
     

    DELPHI-KYLIX ARTICLES

    - Internet Access: Client Service
    - Finishing the Client for an Internet Access ...
    - The Client for an Internet Access Control Ap...
    - User Management for an Internet Access Contr...
    - Important Procedures for an Internet Access ...
    - Server Code for an Internet Access Control A...
    - Constructing the Interface for an Internet A...
    - Building a Server Application for an Interne...
    - Building an Internet Access Control Applicat...
    - Client Dataset: Working with Data Packets an...
    - Using the Client Dataset in an N-Tiered Appl...
    - Using the Client Dataset in Two-Tiered Clien...
    - Using the Client Dataset in File-Based Archi...
    - Demystifying the Client Dataset
    - Working with INI Files in Delphi






    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 4 hosted by Hostway
    Stay green...Green IT