|
Protocol-Independent Name Resolution
In developing a protocol-independent client/server application, there are two
basic requirements that exist with respect to name resolution and registration:
- The ability of the server half of the application (hereafter referred to as a
service) to register its existence within (or become accessible to) one or more
name spaces
- The ability of the client application to find the service within a name space
and obtain the required transport protocol and addressing information
For those accustomed to developing TCP/IP based applications, this may seem to
involve little more than looking up a host address and then using an agreed
upon port number. Other networking schemes, however, allow the location of the
service, the protocol used for the service, and other attributes to be discovered
at run-time. To accommodate the broad diversity of capabilities found in
existing name services, the Windows Sockets 2 interface adopts the model described
below.
Related Links
Software for Delphi and C++ Builder developers
Software for Visual Studio .NET developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET
More Online Helps
Win32 Programmer's Reference (win32.hlp)
Win32 Multimedia Programmer's Reference (mmedia.hlp)
OLE Programmer's Reference (ole.hlp)
Microsoft Windows Pen API Programmer's Reference (penapi.hlp)
Microsoft Windows Telephony API (TAPI) Programmer's Reference (tapi.hlp)
Unix Manual Pages
|
