Purpose of this library

Todays RND managers are faced with a difficult situation when it's comming to choosing which component to use for TCP/IP network communication.

The obvious choice commes to mind: MFC (attached with the full MFC overhead, once you're using it, you can't get rid of it later), .NET (again you're bound forever), Payed solution (which ofcourse are payed solution, without the sources), another open source solutions (either poorly coded, too hard to use, or GPL)

We faced the same problem too, and decided to develop the library which you'll come to understand there's no other solutions like it.

Our library (C++ open source) that encapsulates winsock2 api - allows the user to control every aspect of sockets' operations.

Key features:

• Complete control over TCP/IP header. (allows to modify/craft the headers' flag)

• Complete control over threading scenarios. (Decide how many threads to use, and how to control them )

• Reliable and fast asynchronic sockets. (TCP,UDP and ICMP)

• DNS library. (blocked and asynchronic requests)

• TCP and UDP scanners. (stealth scanning, multithreaded, and regular)

• Domain and IP whois.

• Packet crafter. (craft every packet possible for security tests)

• Ability to switch from asynchronic sockets back to blocking mode.

• Large number of samples to demonstrate the library's abilities.

• Address spoofing.

• TCP/UDP/HTTP relays. (also known as TCP port mapping and UDP port mapping)

• Online code documentation.