[#80531] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...>

SASADA Koichi <ko1@ruby-lang.org> wrote:

24 messages 2017/04/02
[#80532] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/04/02

On 2017/04/02 11:35, Eric Wong wrote:

[#80540] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/04/03

SASADA Koichi <ko1@atdot.net> wrote:

[#81027] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

Eric Wong <normalperson@yhbt.net> wrote:

[#81028] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 9:33, Eric Wong wrote:

[#81029] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 10:53, SASADA Koichi wrote:

[#81031] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

SASADA Koichi <ko1@atdot.net> wrote:

[#81033] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 12:01, Eric Wong wrote:

[#81035] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

SASADA Koichi <ko1@atdot.net> wrote:

[#81042] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/09

On 2017/05/08 15:36, Eric Wong wrote:

[#81044] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/09

SASADA Koichi <ko1@atdot.net> wrote:

[#81045] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/09

On 2017/05/09 12:38, Eric Wong wrote:

[#81047] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/09

SASADA Koichi <ko1@atdot.net> wrote:

[ruby-core:80601] [Ruby trunk Bug#13407] We have recv_nonblock but not send_nonblock... can we add it?

From: samuel@...
Date: 2017-04-07 02:17:45 UTC
List: ruby-core #80601
Issue #13407 has been updated by ioquatix (Samuel Williams).


Okay.

Here is the working example.

~~~
#!/usr/bin/env ruby

require 'socket'

port = 6778

server = UDPSocket.new.tap{|socket| socket.bind("localhost", port)}
client = UDPSocket.new

data = "Matz is nice so we are nice."

t1 = Thread.new do
	packet, (_, remote_port, remote_host) = server.recvfrom(512)
	server.send(packet, 0, remote_host, remote_port)
end

t2 = Thread.new do
	client.send(data, 0, "localhost", port)
	
	response, _ = client.recvfrom(512)
	
	puts "Got response: #{response.inspect}"
end

[t1, t2].each(&:join)

puts "Finished."
~~~

Here is one that fails with EINVAL:

~~~
#!/usr/bin/env ruby

Thread.abort_on_exception = true

require 'socket'

port = 6778

server = UDPSocket.new.tap{|socket| socket.bind("localhost", port)}
client = UDPSocket.new

data = "Matz is nice so we are nice."

t1 = Thread.new do
	puts "Server waiting for packet..."
	packet, (_, remote_port, remote_host) = server.recvfrom(512)
	server.send(packet, 0, remote_host, remote_port)
end

t2 = Thread.new do
	address = Addrinfo.udp("localhost", port)
	
	puts "Sending data to #{address.inspect}"
	# Should call ssize_t sendto(int sockfd, const void *buf, size_t len, int flags, const struct sockaddr *dest_addr, socklen_t addrlen), but calls send which fails with EINVAL.
	result = client.send(data, 0, address.to_sockaddr)
	
	response, _ = client.recvfrom(512)
	
	puts "Got response: #{response.inspect}"
end

[t1, t2].each(&:join)

puts "Finished."
~~~

----------------------------------------
Bug #13407: We have recv_nonblock but not send_nonblock... can we add it?
https://bugs.ruby-lang.org/issues/13407#change-64101

* Author: ioquatix (Samuel Williams)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
We have recv_nonblock, read_nonblock, write_nonblock but not BasicSocket#send_nonblock. Is this a mistake?



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next