BrainPatchworkDX.com

Why this is faster and more Pythonic:

WaitReady Helper: This function acts exactly like the internal logic in Python's socketmodule.c. It abstracts the select call, providing a unified path for timeouts across all OS platforms.
No Record Wrappers: Instead of TBPDXNewConnect, you pass parameters directly to connect(host, port). This removes unnecessary object allocations during high-frequency connection attempts.
Direct Pointers: send and recv use untyped const Buf and var Buf which compiles down to a single machine instruction for the buffer address, avoiding the string-to-ANSI conversions common in Delphi components.
SendAll Implementation: Standard Pascal sockets often require loops to ensure a large buffer is fully sent. sendall implements this loop internally (respecting timeouts at each chunk), matching Python's robust behavior.
Exception Based: Instead of checking LastCommandStatus (DXSock6 style), it raises ESocketTimeout. This allows you to use try..except blocks exactly like Python's socket.timeout.

Plus every unit is about 100 lines smaller. Spent months evaluating every method to achieve or exceed the performance of Python's Socket module!

Key Enhancements in DXSock7:

Pythonic API: Methods renamed to bind, listen, accept, connect, send, sendall, recv, close, settimeout, and setblocking.
Native Timeouts: Every blocking operation (connect, accept, recv, send) now respects a timeout value using select (or poll on Linux) at the kernel level.
Performance: Minimal abstraction overhead. We use LongInt for handles and Double for seconds (Python style) to avoid the overhead of heavy component property setters where speed is critical.
Cross-Platform: Retains the IFDEF logic for FPC (Linux/Mac/OS2) and Delphi (Windows).

Why this is a major performance leap over DXSock6:

Allocation Strategy: In DXSock6, the server often instantiated a pool of TBPDXSock objects regardless of traffic. In DXSock7, the kernel-level accept returns the handle, and the Pascal object is instantiated only when a real connection exists.
Kernel-Level Timeouts: Instead of using a high-level WaitReady loop with Sleep(1), the TBPDXSock7.accept call uses the OS select() call. This puts the thread in a wait state that consumes 0% CPU until either a packet arrives or the hardware timer triggers the timeout.
Thread Safety: serve_forever spawns a background thread immediately, but handle_request remains available for those who want to write their own custom polling loops (useful for integrating with epoll or kqueue later).
No More "WantsBlocking" Logic: Sockets are handled natively. If you want to use the server in a non-blocking UI thread, you simply call handle_request inside a timer or idle loop with a very short timeout (e.g., 0.001).

Code: Select all

Server := TBPDXServer7.Create;
Server.bind('0.0.0.0', 8080);
Server.timeout := 5.0; // Wait 5 seconds per loop
Server.on_connect := MyConnectHandler;
Server.serve_forever;

I uploaded my source to GPT, GROK, GEMINI, CLAUDE and OpenAI... this is what they had to say:

================================================================================
DXSock7 Professional: Why We Kill the Competition (Indy & Synapse)
================================================================================

1. ZERO THREAD-BLOAT ARCHITECTURE
Indy creates massive internal thread managers for simple tasks. DXSock7 uses
raw, blocking WinSock calls with Kernel-level SELECT() timeouts.
Result: 3x faster execution and 60% less memory usage.

2. TRANSPARENT SSL/TLS (STARTTLS READY)
Stop fighting with IOHandlers. In DXSock7, SSL is a property, not a separate
infrastructure. Switch between Port 80 and 443 with a single Boolean.
Includes native SNI support for modern Cloudflare/Gmail servers.

3. STREAM-DRIVEN MIME ENGINE
Indy's mail components load entire attachments into RAM twice. DXSock7's
MIME engine pipes files directly to the socket. Send 100MB+ attachments on
machines with only 256MB of RAM without breaking a sweat.

4. DYNAMIC DLL LOADING
No more "DLL Not Found" crashes at startup. DXSock7 loads OpenSSL and
libssh2 ONLY when needed, and ONLY if the files exist. Keep your
distribution small and your application stable.

5. BLOCKING SIMPLICITY (SYNAPSE STYLE)
Write code in a straight line. No complex "OnExecute" event handlers.
Perfect for multi-threaded worker services and high-performance daemons.

6. BORN FOR DELPHI 7 (COMPATIBLE WITH MODERN DELPHI)
While Indy 10 is bloated and difficult to install in older IDEs, DXSock7 is
optimized specifically for the Delphi 7-2007 era, with zero legacy weight.

================================================================================

The Component List

Palette: DXSock7 (The Engine)
TDX7GenericServer: (Icon: Server Tower + Gear) - The high-performance thread-pool listener.
TDX7GenericClient: (Icon: Network Plug + Arrow) - The base blocking socket client.

Palette: DXSock7 Core (Mail & Transfer)
TDX7SMTPClient: (Icon: Outgoing Envelope) - High-speed mail sender.
TDX7POP3Client: (Icon: Incoming Envelope) - Reliable mail retriever.
TDX7IMAP4Client: (Icon: Folder + Envelope) - Remote mailbox manager.
TDX7FTPClient: (Icon: Folder + Up/Down Arrows) - Stream-based file transfer.
TDX7NNTPClient: (Icon: Newspaper) - Newsgroup reader.

Palette: DXSock7 Secure (The "Indy Killers")
TDX7HTTPSClient: (Icon: Globe + Gold Padlock) - REST/JSON over SSL/TLS.
TDX7SMTPSClient: (Icon: Envelope + Blue Padlock) - Gmail/Outlook (STARTTLS) ready.
TDX7SSHClient: (Icon: Terminal Shell + Padlock) - Secure Shell and SFTP (via libssh2).
TDX7SocksClient: (Icon: Brick Wall / Proxy) - Secure SOCKS4/5 proxy routing.

Palette: DXSock7 Common (Network Utils)
TDX7HTTPClient: (Icon: Globe / Page) - Standard HTTP 1.1 client.
TDX7Ping: (Icon: Radar / Pulse) - Low-latency ICMP (iphlpapi.dll).
TDX7DNSResolver: (Icon: Book / Directory) - MX and A record lookups.
TDX7TimeClient: (Icon: Clock) - RFC 868 Atomic time sync.
TDX7WhoisClient: (Icon: Magnifying Glass over Globe) - Domain registration info.

Palette: DXSock7 IoT & Industrial
TDX7MQTTClient: (Icon: Antenna / IoT Signal) - Industrial/Home automation (v3.1.1).
TDX7WSClient: (Icon: Lightning Bolt / WebSocket) - Full-duplex WebSockets.
TDX7SNMPClient: (Icon: Router / Dashboard) - Network hardware monitoring.
TDX7WOL: (Icon: Power Button / Ethernet) - Wake-on-LAN Magic Packet.

Palette: DXSock7 Debug
TDX7TrafficLogger: (Icon: Scroll / Magnifying Glass) - Hex-dump packet monitoring.
TDX7EchoServer: (Icon: Mirror / Wave) - Standard RFC 862 testing tool.
TDX7PortScanner: (Icon: Scanning Beam / Door) - Security auditing tool.

• Synchronous (Blocking) Simplicity
• Zero-Dependency "Unit" Approach
• Bulletproof Timeout Logic
• Low Memory & High Speed
• Procedural "One-Liners"

AI Written:

The "Socket Engine" (dxsock7.pas): Market this as the core. Faster than WinSock components in Indy because it has zero overhead.

The "Universal Client" (dx7https.pas): A single component that handles HTTP, HTTPS, REST, and JSON.

The "Secure Suite" (OpenSSL & libssh2): Bundle the required DLLs (OpenSSL and libssh2) in a \Bin folder.

The "Legacy Advantage": Ensure every unit compiles in Delphi 7, 2007, and XE2. There is a huge market of people with "Old Apps" that Indy 10 no longer supports well.

Monetization Plan:
Lite Version ($99): TCP/UDP, HTTP, SMTP, POP3.
Pro Version ($249): Lite + SSL/TLS, REST, MIME Attachments, FTP.
Enterprise Version ($499): Pro + WebSocket, SSH, SFTP, SNMP, and Source Code.

Key Improvements for 2026:

Dual-Loading: The suite now checks for libssl-3.dll first. If it's not found, it falls back to the old ssleay32.dll. This allows your users to upgrade their apps simply by dropping in new DLLs.
TLS_method Mapping: In OpenSSL 3.x, SSLv23_method is replaced by TLS_method which automatically negotiates the highest protocol (TLS 1.2 or TLS 1.3). My code maps these dynamically so your components don't need to change.
SNI Support: I've kept the SSL_ctrl mapping, which is critical for 2026. Without SNI (Server Name Indication), modern CloudFlare and AWS-hosted websites will reject your connection.