Just got done building some shit they told me I couldn't. Code: Server listening on port 9900. Press any key to terminate the server process... Client connection accepted. There are 1 clients connected to the server Received: "ab2abac0-9044-48e9-9307-51ae0b951baa|*|STRT". The server has read 43 bytes. Received: "ab2abac0-9044-48e9-9307-51ae0b951baa|*|Message :: aaaaajhasdjhgjksahg kl". The server has read 71 bytes. Received: "ab2abac0-9044-48e9-9307-51ae0b951baa|*|adjvnmnalsdgndlsghbvnsejlthgxs ng". The server has read 71 bytes. Received: "ab2abac0-9044-48e9-9307-51ae0b951baa|*|fuehga;dhtuwe". The server has read 52 bytes. Received Composite: "Message :: aaaaajhasdjhgjksahgkladjvnmnalsdgndlsghbvnsejlth gxsngfuehga;dhtuwe". The server has read 77 bytes. Received: "ab2abac0-9044-48e9-9307-51ae0b951baa|*|STOP". The server has read 43 bytes. This is using SocketAsyncEvent architectures, like RunUO. This difference here is instead of sending a fixed block of bytes that are restricted to your buffer size, this breaks up your data into smaller segments, creates an object that holds all these segments, and then upon getting the notification that it's complete ('|*|STOP') it consolidates all these smaller segments into the full message. At first it was to allow for the transfer of large files (which is people on stack overflow literally told me I couldn't do, was impossible, etc). But now I'm going to run it against the the same server logic using using standard fixed buffer sizes like you'll find on codeproject.com, and see how the operational speed and load capabilities compares because it seems pretty quick and sending 50 bytes twenty times may be faster than sending 1000 bytes once due to the nature of TCP, loops, and networking in general. I'll keep you guys updated.