On Nov 18, 2010, at 8:04 PM, Charles Oliver Nutter wrote:

> when a channel
> we don't own enters Ruby, we wrap it, and then our finalization closes
> it prematurely. In an effort to fix that bug, I eliminated "close"
> from our finalization of those channel wrappers

Suggestion:  Make the "close" behavior optional, per wrapper.
Only set the "mustClose" bit on channels created via Ruby APIs.

-- John

-- 
You received this message because you are subscribed to the Google Groups "JVM 
Languages" group.
To post to this group, send email to jvm-langua...@googlegroups.com.
To unsubscribe from this group, send email to 
jvm-languages+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/jvm-languages?hl=en.

Reply via email to