apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norman Tuttle" <nltut...@gmail.com>
Subject Re: apr_socket_recvfrom question
Date Tue, 24 Oct 2006 16:20:04 GMT

(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:

A post from Ruben H. in April also pointed up the same problem:

-Norman Tuttle NLTuttle@gmail.com

On 10/24/06, David Horowitz <davidh@mcgrawsoftware.com> 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

View raw message