DXSock 6th Generation.

[ONiX]

During a contract (2005ish) with a client that used DXSock 3 to run his business. I found myself learning to swim in the Deep end of the pool ~ Linux. My first task was to stabilize their Modem rack. My first "hands on" working with Remote TCP modems. (20+ years later, I am doing this for a living).

Anyway, I dove in head first ~ to developing with Free Pascal. After a couple of weeks of Googling their web site ~ I found the pieces I needed to rebuild DXSock. I was developing on a 21" Mac Book Pro... a nice laptop!! So, I launched vim, and started coding ~ making a fairly large

$IFDEF

structure - I began replacing Winsock hooks with the similar commands for UNIX systems. A couple weeks in, I was ready to redesign the DXSOCK SERVER CORE design using Posix Threads.

A month in, I bumped the version to DXSock 5.5 (I had made DXSock 5.0 for my previous employer (CODY Systems)).

5.5 was already processing over 100,000 connections a day. No memory leaks, no failed connections. I bought a Web Server tester (Socrates), and built a new version of my "Winshock Web Server". Socrates was capable of concurrent tests ~ this would help me flesh out any bugs in my thread-pools.

2006, this contract became full-time employment making double what my previous employer could afford to pay me. Being a new year, and a new product (in my eyes)... DXSock became DXSock 6. The smallest build I had ever made.

G.E. Ozz Nixon Jr.
CEO Brain Patchwork DX, LLC.

[ONiX]

My next task was to learn OpenSSL 0.9.8 ~ and implement it as simple as possible. I did!

DXSock 6.0 introduced a new procedure, EnableEncryption(...). And when you were finished for solutions that had STARTTLS sessions. You could DisableEncryption(...).

Requirements:
[*] Make the product work with Linux ✓
[*] Remove Borland Dependencies ✓
[*] Simplify the Server ✓
[*][*] Support Running in the Background, or simply running ✓
[*] Remove the 100+ Protocol Implementations ✓