From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randi Subject: UDP data Date: Thu, 10 Feb 2011 10:41:02 +0700 Message-ID: <1297309262.2205.14.camel@godart> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=KZLU9LAKuCl8BOzkyWEB+IgvOvp/howXcM9PsUAkO68=; b=Jk0N/hW/veFJEe/eHRkaeAghPISKMoR7xvQaljPagL5LtSevf1OFEYyq4Nxd/OVXXx 5Zhg+hhhDUKGD+QOSROJdvVQ07EvUWzs5dTZiw4KY8UI7dlAb3EoueTdnptREKgbwku7 11eyGFL6yKCk/qbTOMnMkvC49rajlB6c3ROx0= In-Reply-To: Sender: linux-c-programming-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: linux-c-programming@vger.kernel.org Hi All, Since UDP socket is not reliable, what the common way in user level to check UDP communication's data for error (eg. malformed, corrupted, etc.)? is the checksum field in the UDP header (struct udphdr) intended to this problem? Randi