Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!gegeweb.org!aioe.org!.POSTED!not-for-mail From: Ralph Spitzner Newsgroups: comp.os.linux.networking Subject: Re: Data sent through sockets are *sometimes* inverted ?!!! Date: Thu, 23 Feb 2012 17:03:47 +0100 Organization: Hanswurst & Kaspar Hauser Ltd. Lines: 28 Message-ID: <2l4i19-uvm.ln1@spitzner.org> References: <435969f4-8cf5-44d7-a46e-64c0a20223a8@e27g2000vbu.googlegroups.com> <1bsji9i43k.fsf@pfeifferfamily.net> <1b1upq6ssg.fsf@pfeifferfamily.net> NNTP-Posting-Host: hHjA4DcVYoA8Gqbq3XyaYQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Firefox/10.0.2 SeaMonkey/2.7.2 X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.networking:1089 Jorgen Grahn wrote: [...] > The question is "under which situations does write() on a TCP socket > return a partial write?". ("Partial write" meaning that some, but not > all of the data you fed it got sent.) Well if the connection somehow gets interrupted write will return a number less that the number of bytes you fed to it. [....] > Why? TCP doesn't lose bytes[1]; only programming errors cause that. > > /Jorgen > > [1] Except the rare cases where packets get corrupted in transit > in such a way that the checksum is still valid. > Well yes, but the OP _believes_that TCP is doing some evil to his data, apart from this not being true and not knowing his programming techniques and/or skills, a checksum might help him :-P -rasp -- RTMPDump & ffmpeg are your friends.. -icke