Click here to Skip to main content
Click here to Skip to main content
Add your own
alternative version

TCP/IP Protocol Design: Message Framing

, 25 Jun 2009
Why a single "Send" does not necessarily result in a single "Receive", and how to compensate.
No downloads associated with this content

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Stephen Cleary
Software Developer (Senior) Nito Programs
United States United States
Stephen Cleary is a computer programmer living in Northern Michigan. He enjoys reading and is actively involved in his church. On October 4th, 2008, he married Amanda Snell, and he is happy about that. Smile | :)
 
Programming blog: http://nitoprograms.blogspot.com/
(including the TCP/IP .NET Sockets FAQ: http://nitoprograms.blogspot.com/2009/04/tcpip-net-sockets-faq.html )
CodePlex project leads on:
Nito Async Library: http://nitoasync.codeplex.com/
Nito MVVM Library: http://nitomvvm.codeplex.com/
Personal home page: http://www.stephencleary.com/

| Advertise | Privacy | Mobile
Web04 | 2.8.140827.1 | Last Updated 25 Jun 2009
Article Copyright 2009 by Stephen Cleary
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid