From dev-return-17422-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Thu Oct 26 06:42:54 2006 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 18635 invoked from network); 26 Oct 2006 04:44:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Oct 2006 04:44:33 -0000 Received: (qmail 5316 invoked by uid 500); 24 Oct 2006 16:20:40 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 5282 invoked by uid 500); 24 Oct 2006 16:20:39 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 5260 invoked by uid 99); 24 Oct 2006 16:20:39 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2006 09:20:39 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of nltuttle@gmail.com designates 66.249.82.225 as permitted sender) Received: from [66.249.82.225] (HELO wx-out-0506.google.com) (66.249.82.225) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2006 09:20:25 -0700 Received: by wx-out-0506.google.com with SMTP id i27so2114480wxd for ; Tue, 24 Oct 2006 09:20:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=I2xiUvwvmX+90JAywUIWFdA4IgC8BV63Terbb89720TGhHQsRzNrY2vEkr6WDcw6vm/1coIfE6C3z3eGV8bY8llgY//XSVq1BfCE7oT8Aqp37DgKPYdz+YK2twMj0zNvkj4xWzl4hFnntrvEDDn1V+wTEIlE0LdNBGyOYmhtVM8= Received: by 10.90.79.6 with SMTP id c6mr3225147agb; Tue, 24 Oct 2006 09:20:04 -0700 (PDT) Received: by 10.90.31.3 with HTTP; Tue, 24 Oct 2006 09:20:04 -0700 (PDT) Message-ID: Date: Tue, 24 Oct 2006 12:20:04 -0400 From: "Norman Tuttle" To: "David Horowitz" Subject: Re: apr_socket_recvfrom question Cc: dev@apr.apache.org In-Reply-To: <03e101c6f785$6e059b10$6501a8c0@Ryan> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <03e101c6f785$6e059b10$6501a8c0@Ryan> X-Virus-Checked: Checked by ClamAV on apache.org David: (Re: apr_socket_recvfrom() function) I already pointed out a bug in this function. I have not had any time to fix the problem, and my company chose not to use APR for our project in the end. Perhaps you can apply the bug fix. See my post in the archive: http://mail-archives.apache.org/mod_mbox/apr-dev/200608.mbox/%3ce7fa31290608201939t103c0686xb211e4ade2b41e64@mail.gmail.com%3e A post from Ruben H. in April also pointed up the same problem: http://mail-archives.apache.org/mod_mbox/apr-dev/200604.mbox/%3c443CE399.2080800@area99.dk%3e -Norman Tuttle NLTuttle@gmail.com On 10/24/06, David Horowitz wrote: > Hi folks, > > I'm wondering about apr_socket_recvfrom, specifically the "from" parameter. > > It is understood that "from" returns the apr_socketaddr_t of the sending > socket upon return. However, I see discrepancies on whether "from" has any > significance as an input parameter. > > APR test code indicates the "from" parameter is used as an input-output > parameter, indicating upon input the sockets from which we are willing to > receive data. > > However, recvfrom(2) man page makes no mention of "from" as anything other > than an output parameter, and even mentions it can be NULL if you don't care > about the sender's identifying information. > > So, my question: is "from" indeed an input-output parameter, or just an > output parameter? Again, I confirm APR test code indicates it's both, but if > recvfrom(2) doesn't treat it as such, than apr_socket_recvfrom() obviously > won't either. > > Does anyone have clarity on this subject? > > Thank you, > > David > > > > >