|
Overview of Windows Sockets 2
Windows Sockets 2 utilizes the sockets paradigm that was first popularized by
Berkeley Software Distribution (BSD) UNIX. It was later adapted for Microsoft
Windows in the Windows Sockets 1.1.
One of the primary goals of Windows Sockets 2 has been to provide a
protocol-independent interface fully capable of supporting the emerging networking
capabilities, such as real-time multimedia communications.
Windows Sockets 2 is an interface, not a protocol. As an interface, it is used
to discover and utilize the communications capabilities of any number of
underlying transport protocols. Because it is not a protocol, it does not in any way
affect the "bits on the wire", and does not need to be utilized on both ends
of a communications link.
Windows Sockets programming previously centered around TCP/IP. Some of the
programming practices that worked with TCP/IP do not work with every protocol. As
a result, the Windows Sockets 2 API added new functions where necessary.
Windows Sockets 2 has changed its architecture to provide easier access to
multiple transport protocols. Following the Windows Open System Architecture
(WOSA) model, Windows Sockets 2 now defines a standard service provider interface
(SPI) between the application programming interface (API), with its functions
exported from WS2_32.DLL, and the protocol stacks. Consequently, Windows Sockets 2
support is not limited to TCP/IP protocol stacks as is the case for Windows
Sockets 1.1. For more information, see Windows Sockets 2 Architecture.
There are new challenges in developing Windows Sockets 2 applications. When
sockets only supported TCP/IP, a developer could create an application that
supported only two socket types: connectionless and connection-oriented.
Connectionless protocols used SOCK_DGRAM sockets and connection-oriented protocols used
SOCK_STREAM sockets. Now, these are just two of the many new socket types.
Additionally, developers can no longer rely on socket type to describe all the
essential attributes of a transport protocol.
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|