[#3006] CVS repository — "Eugene Scripnik" <hoaz@...>

Hello.

21 messages 2004/06/16
[#3008] Re: CVS repository — ts <decoux@...> 2004/06/16

>>>>> "E" == Eugene Scripnik <hoaz@gala.net> writes:

[#3009] Re: CVS repository — Michal Rokos <michal@...> 2004/06/16

Hi!

[#3057] Ruby 1.8.2 to be released. — matz@... (Yukihiro Matsumoto)

Hi,

20 messages 2004/06/23

Re: I think I found the recvfrom problem!!

From: Dave Thomas <dave@...>
Date: 2004-06-23 13:14:26 UTC
List: ruby-core #3051
On Jun 22, 2004, at 18:41, Yukihiro Matsumoto wrote:
> First of all, patch seems OK.  Please commit.

Will do..

> According to this description, TCP socket (that must know their source
> address) should give us the peer address even for non connection
> oriented sockets.  I feel like it's a bug in BSD socket layer.  Does
> anyone know if it's an unspecified behavior in POSIX socket
> definition, that can be vary between platforms, or a bug in either
> platform?

Perhaps it's a performance thing? As you can always get the peer 
address of a TCP connection, there's no need to return it every time 
you receive data.

I had a quick look through Stevens--he only used recvfrom for 
connectionless examples.

Solaris seems to return a 'from' parameter for all connections, as does 
HPUX. So, I think I agree that it's a strangeness on the part of BSD.

Cheers

Dave


In This Thread