Hi! It's actually not something that is entirely controlled in the server or client (unless you use raw sockets), this can happen due to the way I/O buffering happens in the operating system. A client/server can buffer things up and issue a single write() system call in hopes they stay together, but the OS/network could still break them up due to fragmentation or maximum segment size. Also, multiple write()'s could be grouped into a single packet if the TCP delay is enabled (usually don't want to set this due to latency).
So, it happens, yes, but it's not really a relevant question. -Eric On Wed, Oct 07, 2009 at 04:26:38PM -0700, Dustin wrote: > > > On Oct 7, 4:23 pm, Daniel Nichter <[email protected]> wrote: > > > Does the memcached protocol support multiple commands in a single TCP > > packet? The protocol doc (http://code.sixapart.com/svn/memcached/ > > trunk/server/doc/protocol.txt) says this is possible with UDP, but I > > have a case where TCP packets contain multiple commands. For example > > (some data changed to protect the innocent): > > Absolutely. My client relies on this for both TCP-based protocols.
