An overview of the Packages and Assemblies in the Internet Direct (Indy) source code. 

The source code in the Indy 10 library has been reorganized into the following packages: 

• IndySystem
• IndyCore
• IndyProtocols
• IndySuperCore (for use with Delphi 7 only)

Each package (and the source files used in the package) are stored in separate directories. For example, Delphi 2005 could have Indy package files and source code in the following directories: 

Each package includes a run-time .DPK file for Delphi compiler versions 4, 5, 6, 7, 2005 (and beyond). For packages that also include installable IDE components, there is also a design-time .DPK file for Delphi compiler versions 4, 5, 6, 7, 2005 (and beyond). 

The compiler version is used as a suffix in the package file name. For example, Delphi 2005 (compiler version 9.0) uses the suffix '90' in all package file names. 

If you are using a version of Indy.Sockets that is installed along with the Borland Developer Studio 2006 IDE and compilers, the compiler verison suffix is omitted from the package names. For Instance: 

The IndySystem package (IndySystemXX.dpk) provides system-level support for constructs used in the Indy library. For instance: 

• Winsock2 header translations
• Socket handle classes for supported platforms
• Stream implementations for VCL and .Net
• Run-time library support classes for VCL, VCL.Net, and the .Net FCL
• Utility Classes/Procedures/Functions
• Exceptions
• The base component in the Indy library
• GUI integration classes for blocking socket operations

The IndyCore package includes the essential base classes and components needed to implement ICMP, TCP, and UDP clients or servers, including: 

• Buffers used for reading and writing in the Indy library
• An ICMP client
• A TCP client and server
• A TCP client and server that implement support for command handlers
• A UDP client and server
• IP address classes
• IOHandlers
• Intercepts
• Logging components
• RFC-compliant message response formats
• Threads
• Thread-safe data types
• A design-time GUI integration class

The IndyCore package does not include support for any of the higher-level protocols. 

The IndyProtocols package implements classes need to create and support clients and servers for Internet Standard protocols, like: 

The IndySuperCore package provides support for advance functionality available on Windows server platforms for the Fibers API, I/O Completion Ports, and chained IOHandlers. 

The IndySuperCore package is designed to aid in creating more scalable servers where thousands of simultaneous client connections are required. 

Fiber and IOCP APIs are supported only for the Windows 2000, 2003, and XP operating systems using Delphi version 7. Windows 95, 98, and ME are not supported. Delphi compilers prior to version 7 are also unsupported due to critical changes in the VCL since those releases. 

For more detailed information about differences in the implementations for the Indy 9 and Indy 10 libraries, please refer to the "Migrating to Indy 10" section in the documentation. 

Indy.Sockets is developed using the Delphi programming language (formerly know as Object Pascal). Borland IDE users can compile packages and assemblies using the package files included in the source code for the library. For users on .NET platform that do not include support for the Delphi language (including VS.NET and Mono), the Indy.Sockets.DLL pre-compiled assembly is available from the Indy website.