winsock sockets c

C++ Sockets is a C++ wrapper for BSD-style sockets.

Here are some key features of "Cplusplus Sockets":

· SSL support
· IPv6 support
· tcp and udp sockets
· encrypted tcp
· http protocol
· highly customizable error handling

Whats New in This Release:

· A fatal bug in LineProtocol/Online when a CRLF happened over a read buffer boundary has been fixed.
· New output buffer logic.
· OnWriteComplete callback has been added, which fires after the output buffer has been transferred.

Simple Sockets Library provides a simple C programming interface to sockets.

The Simple Sockets Library makes sockets easy to use and comes as public domain source code. It resembles Cs file I/O, uses whatever port is available, has named servers and port reuse, streaming/blocking sockets used, polling support, blocking/selection support via numerous functions, timeout control and firewall support.

Here are some key features of "Simple Sockets Library":

· Resembles Cs file i/o:
· Sclose() Sgets() Sopen() Sprintf() Sputs() Sread() Sscanf() Swrite() Svprintf()
· Uses currently available ports only, so if a server can be brought up, it will be
· Named sockets -- servers have names, not fixed port addresses!
· (no more REUSEADDR problems, linger setting, zombie sockets!)
· Streaming/blocking sockets used
· Polling supported (ie. avoids blocking):
· Stest() Smasktest() Speek()
· Numerous functions to handle multiple concurrent clients:
· Smaskfdset() Smaskpush() Smasktime() Smaskunset() Smaskwait()
· Smaskget() Smaskset() Smaskunfdset() Smaskuse() Sprtmask()
· Smaskpop() Smasktest()
· Timeout control:
· Stimeoutwait() Smasktime()
· The PortMaster (Spm): Maintains a distributed port/server-name database Each machine runs a PortMaster which maps servers by name to their ports (transparent to programmers and users!)
· Firewall Support
· The PortMaster can (optionally) only "put through" connections from approved machine sites
· Supports "path"ing for sockets: one can use an environment variable to track down a server, by name, on any machine in a group:
· Sopenv()
· Doesnt need root privileges (thats Unix lingo...)
· Now supports fixed ports (servers and/or clients) to facilitate interfacing to non-SSL servers/clients

The Simple Sockets Librarys main purpose is to provide an Application Programming Interface that strongly resembles the standard C librarys file handling interface. Thus programmers find that the Simple Sockets Librarys learning curve is particularly short. As a secondary purpose the Simple Sockets Library helps programmers avoid some common programming problems with sockets (avoided: large buffers that dont transfer in their entirety without special effort, the Nagle algorithms practical effect of often limiting one to five transfers per second, servers whose ports refuse to re-open until two minutes have passed, etc). Strings are null-byte terminated just like regular C/C++ strings, facilitating their ease of use in C/C++ programming.

The Simple Sockets Library preferentially uses names for its servers rather than requiring hard-coded port numbers. Imagine if, instead of files having names, everyone went about saying "use sector 4 and track 14" or somesuch thing. This situation reflects what we now have with sockets -- and when two programs use the same port number for their servers, they cant co-exist simultaneously on a system. However, especially for those whose programs must interface with other programs using hard-coded port numbers, the Simple Socket Library also supports hard-code port numbers.

The Simple Sockets Library opens streaming sockets. Thus the Simple Sockets Librarys sockets provide guaranteed delivery of information in the correct order (unlike datagrams, for example).

The PortMaster (Spm), source code for which is part of the library, provides a "phonebook" to map server names to dynamically allocated port numbers. Port numbers thus wont clash; the operating system determines which ones are currently available and the PortMasters effectively publish the result.

Whats New in This Release:

· (Marcel Satchel) improved c> c> for Windows
· (Aug 22, 2005) included the "b" option for Sopen() (block until requested server becomes available)
· (Marcel Satchel) Sinit.c fixed (yet again!)

Connecting Sockets (CSockets) is a Windows© 98/ME/2000/NT program which uses the winsock to make connections to a user specified server and port and exchange text commands. CSockets can also create a listening socket at a user specific port and accepts clients. Futhermore CSockets can check a server and see which ports are open. A great program to test your own protocols or to test servers and clients. The shareware version has some limitations to encourage you to buy the product.

The Winsock Interface Library for C/C++ simplifies winsock network communications development and provides support for the most common Internet protocols such as Finger, SMTP, POP3, FTP, NNTP, TELNET, and HTTP. Requires windows C/C++ compiler (Microsoft, Borland, or Watcom). Documentation (3 manuals) comes in three formats: text, Word97, and HTML. Registration is $105 for email delivery.

WIL4C can be used in the development of Win16 and Win32 applications running under Windows 3.1, Windows 95/98/2000, and Windows NT 4.0. The shareware version of WIL4C is fully functional.

Urthmans Sockets Database v1.00.0027 was designedinitially as a Visual Basic developers database of commonly used port assignments. This software has the potential to aid in the maintenance of your networks/etc/services file. Reads and writes ASCII files of the appropriate format. Includes RFC-1060 and RFC-1700 data.

Build your own scalable Internet/Intranet server application in .NET with every connection getting an individual thread. Easy-to-use TCP and UDP components allow for Internet client applications with only a few lines of code and convenient Events.

The Ping component allows server verification using ICMP, UDP, and TCP, while the Trace component conducts an asynchronous Trace Route for fast response.

The Dns component is not dependent on OS services, allowing for the use of any DNS server. Advanced SegmentedStream technology allows for data to be received up to a specific delimeter or fixed-length, which is ideal for building custom TCP-based protocols.

Here are some key features of "PowerTCP Sockets for dotNET":

· 100% managed code!
· AutoReceive technology reduces code by managing all incoming data.
· On-the-fly data parsing and Event notification with the TCP component.
· Supports SOCKS4 and SOCKS5 proxies.
· High server performance with every connection receiving a separate thread (tested to accept over 75 connections per second).
· Designed for usage on the desktop, in a Web Service, or in ASP.NET.
· Unique asynchronous UDP send/receive capability enhances what is provided in the Microsoft .NET Framework.
· EnhancedStream and PipeStream classes allow developers to create their own powerful streams.
· Look-ups, reverse address look-ups, and mail address look-ups (from MX records) with user defined DNS servers using the Dns component.
· Ping component allows for host verification using ICMP, UDP, and TCP protocols.
· Trace component supports asynchronous echoes for unprecedented trace route performance.
· Each component architected to take advantage of .NET object-oriented capabilities.
· Each component has multi-threaded asynchronous functionality.
· Each component allows user-interface events to process during synchronous use.
· Each component is thread-safe on critical members.
· Supports International character sets.
· Debugging has been extended beyond run-time testing to a design-time Editor in every component to allow connectivity to be tested without compiling. Properties set in the Editor are recorded directly in the code, and a real-time feedback window gives detailed information about results.
· Includes a royalty-free license.
· Over 2 dozen tutorials and a comprehensive reference guide with full support for dynamic help are included with the integrated Help 2.0 documentation.
· Supports VS.NET, Delphi 8, C# Builder, and other .NET compliant development environments.


Limitations:

· 30 days free trial

TracePlus/Winsock is a powerful application-level performance and diagnostic tool for Win32 platforms.

Featuring an integrated data analyser, TracePlus moves beyond the realm of displaying API calls, being both a full-featured Winsock spy and data analysis tool.

Using its unique visual realtime display of Winsock activity, you can spot timing-sensitive Winsock problems, view error codes for failed Winsock functions, reverse engineer other Winsock applications without source code, interpret conversations between two Winsock applications, and learn how Internet protocols are implemented.

TracePlus will prevent a program from detecting that it is being run in a debugger.

Some well known applications have code in them that prevent applications such as TracePlus from revealing the way that they operate. Such applications abort immediately after they are launched, or disable certain features of the application when a debugger is detected.

TracePlus is aware of several different methods by which applications can detect whether they are being debugged. Via these same techniques, TracePlus indicates to the application that in fact it is not being debugged. Such applications will then run normally inside of TracePlus.

Here are some key features of "TracePlusWinsock":

· Detailed information on each call to the Winsock 2 API as well as the Microsoft Winsock extensions.
· Detailed information on each call made to the Win32 Internet API (WININET). In addition, several of the WININET API functions will display the data packet associated with that function in the Data View.
· Detailed information on each call made to the Remote Access Services (RAS) API.
· Detailed information on standard Win32 File I/O API functions when socket numbers are passed instead of file handles.
· WSAAsyncxxx() calls are monitored, and detailed information is provided on each posted asynchronous notification and statistics are provided on response time.
· Full IPV6 Support. TracePlus/Winsock can distinguish between IPV4 and IPV6 addresses and display each one in the appropriate format. IPV6 socket options are recognized in the Socket View.
· Detailed information on each call to an I/O completion routine, including statistics on response time.
· Novell IPX Support. Peer addresses are formatted in IPX format. Microsoft specific IPX socket options are recognized in the Socket View.
· Full support for I/O completion ports. Calls to CreateIOCompletionPort(), GetQueued(), and PostQueued() are monitored, and queued packets will be displayed in the Data View
· Supported API functions that fail are indicated in the Diagnostics View along with the Winsock or Win32 error code describing the failure
· Displays Winsock traffic originating from Java applets and Javascript embedded in a Web page
· Displays Winsock traffic originating from ActiveX controls and COM objects instanced by an application.
· Detailed information on all Winsock, RAS, and WININET API calls originating from a child process
· Works with most commercial Win32 applications (release versions) with no modifications to the target application
· Compatible with Microsoft Terminal Server (Windows NT 4.x, Windows 2000, Windows 2003 Server)
· Works with most Win32 Services on platforms that support services (Windows NT 4.x, Windows 2000, Windows XP, Windows 2003 Server)
· Supports Win32 .EXE files from all languages and compilers (including Visual C++, Visual Basic, Visual C#, Microsoft Access, MASM, Borland Delphi and C++ Builder, Sybase PowerBuilder)
· Session view displays detailed information about each data packet sent or received during a session between your PC and the host machine. A Session is defined as all data transferred via a single socket.
· DNS Lookup View displays statistics on the calls made by the application to translate a domain name (www.anydomain.com) to an IP address.
· Connect Times View displays statistics on the amount of time taken by the server to acknowledge a connection request made by the application.
· Microsecond timing accuracy on Windows NT 4.x, Windows 2000, Windows XP, and Windows 2003 Server.
· User definable filter profiles enable separate API configurations for different capture sessions
· Displays the server (peer) IP address for all API function calls, socket states, and data packets

*C/C++ interpreter

Ch supports C99 and C++ classes. Ch supports many industry standards with over 8,000 functions including POSIX, socket/Winsock, X11/Motif, OpenGL, ODBC, C LAPACK, GTK+, Win32, and CGI.

* Shell programming and cross-platform scripting

Ch shell is C compatible shell while C-shell (csh) is a C like shell. Ch is an interpretive implementation of C, similar to Unix/MS-DOS shells. Ch in Windows includes over 100 commonly-used Unix commands for portable shell programming. Ch can also be used as a login shell just like sh, csh and ksh. Ch bridges the gap between the C language and shell languages. With its built-in string type and many enhanced scripting features, Ch is an alternative to other scripting languages for automating repetitive tasks, regression test, and hardware testing.

* 2D/3D plotting and numerical computing

Ch supports 2D/3D graphical plotting, C LAPACK, high level numeric functions.
Ch has built-in 2D/3D plotting support, generic mathematical functions and computational arrays for linear algebra and matrix computations, and advanced high-level numerical functions for linear systems, differential equation solving, Fourier analysis, curve fitting, etc.

*Interface with binary C/C++ libraries

Ch SDK 4.5 can easily integrate the existing C/C++ libraries as part of Ch sripting module. Functions and classes in static or dynamical libraries can be invoked in a Ch script file or Ch command shell.

* Embeddable scripting

Ch 4.5 is optimized for embedded scripting. Embedded Ch allows users to embed Ch into other C/C++ application programs and hardware. It is ideal for game and open-architecture application integration. With Embedded Ch, C/C++ applications can be extended with all features of Ch. It allows execution of C/C++ scripts generated dynamically on-line. Embedded Ch has a small footprint.

TracePlusWinsock description
A software application that shows you the interaction between your Win32 application and the 32 bit Winsock API TracePlus/Winsock is a powerful application-level performance and diagnostic tool for Win32 platforms.

Featuring an integrated data analyser, TracePlus moves beyond the realm of displaying API calls, being both a full-featured Winsock spy and data analysis tool.

Using its unique visual realtime display of Winsock activity, you can spot timing-sensitive Winsock problems, view error codes for failed Winsock functions, reverse engineer other Winsock applications without source code, interpret conversations between two Winsock applications, and learn how Internet protocols are implemented.

TracePlus will prevent a program from detecting that it is being run in a debugger.

Some well known applications have code in them that prevent applications such as TracePlus from revealing the way that they operate. Such applications abort immediately after they are launched, or disable certain features of the application when a debugger is detected.

TracePlus is aware of several different methods by which applications can detect whether they are being debugged. Via these same techniques, TracePlus indicates to the application that in fact it is not being debugged. Such applications will then run normally inside of TracePlus.

Here are some key features of "TracePlusWinsock":

· Detailed information on each call to the Winsock 2 API as well as the Microsoft Winsock extensions.
· Detailed information on each call made to the Win32 Internet API (WININET). In addition, several of the WININET API functions will display the data packet associated with that function in the Data View.
· Detailed information on each call made to the Remote Access Services (RAS) API.
· Detailed information on standard Win32 File I/O API functions when socket numbers are passed instead of file handles.
· WSAAsyncxxx() calls are monitored, and detailed information is provided on each posted asynchronous notification and statistics are provided on response time.
· Full IPV6 Support. TracePlus/Winsock can distinguish between IPV4 and IPV6 addresses and display each one in the appropriate format. IPV6 socket options are recognized in the Socket View.
· Detailed information on each call to an I/O completion routine, including statistics on response time.
· Novell IPX Support. Peer addresses are formatted in IPX format. Microsoft specific IPX socket options are recognized in the Socket View.
· Full support for I/O completion ports. Calls to CreateIOCompletionPort(), GetQueued(), and PostQueued() are monitored, and queued packets will be displayed in the Data View
· Supported API functions that fail are indicated in the Diagnostics View along with the Winsock or Win32 error code describing the failure
· Displays Winsock traffic originating from Java applets and Javascript embedded in a Web page
· Displays Winsock traffic originating from ActiveX controls and COM objects instanced by an application.
· Detailed information on all Winsock, RAS, and WININET API calls originating from a child process
· Works with most commercial Win32 applications (release versions) with no modifications to the target application
· Compatible with Microsoft Terminal Server (Windows NT 4.x, Windows 2000, Windows 2003 Server)
· Works with most Win32 Services on platforms that support services (Windows NT 4.x, Windows 2000, Windows XP, Windows 2003 Server)
· Supports Win32 .EXE files from all languages and compilers (including Visual C++, Visual Basic, Visual C#, Microsoft Access, MASM, Borland Delphi and C++ Builder, Sybase PowerBuilder)
· Session view displays detailed information about each data packet sent or received during a session between your PC and the host machine. A Session is defined as all data transferred via a single socket.
· DNS Lookup View displays statistics on the calls made by the application to translate a domain name (www.anydomain.com) to an IP address.
· Connect Times View displays statistics on the amount of time taken by the server to acknowledge a connection request made by the application.
· Microsecond timing accuracy on Windows NT 4.x, Windows 2000, Windows XP, and Windows 2003 Server.
· User definable filter profiles enable separate API configurations for different capture sessions
· Displays the server (peer) IP address for all API function calls, socket states, and data packets


Requirements:

· Pentium 3 or AMD Athlon 1 GHZ or greater
· 192 MB RAM
· 10 MB disk space


Limitations:

· Starting or cleaning Captures will be disabled after 40 minutes
· API functions in the Diagnostics View will be fully visible for the first 20 items.
· Certain statistics in all views will be fully visible for the first 20 items
· Save feature is disabled

COM library for Visual Basic 6, providing an easy access to the network layer of operating system (UDP and TCP sockets).

OSWINSCK.dll serves as a wrapper for Winsock API and helps programmers to abstract from complexity of API calls and concentrate on application functionality.