@tmm1 just thought I'd let you know that I've completely solved the issues with connection weirdness and eventmachine on windows.

The FD_SETSIZE must be the same on ruby installer as it is in eventmachine.
The next release of ruby installer will increase the limit to 32767 so this must be reflected in project.h
Previous versions of ruby installer ruby will continue to work as they used to.

Thanks for your on going help in the matter. Very much appreciated and helpful.
I'll also stop harassing you now too. ;)

The ruby installer issue oneclick/rubyinstaller#104

@tmm1 the final product rolled out at Sydney University running on eventmachine and rubyinstaller ruby.
I did a little write up on the project.

https://groups.google.com/forum/?fromgroups#!topic/rubyinstaller/0UlbSlwXa6U

why does it have to match the rubyinstaller FD_SETSIZE again?

From observations on Windows 2008 R2 x64 VM

1. Ruby SETSIZE < EM SETSIZE

• Ruby SETSIZE is enforced
• Unpredictable behaviour beyond Ruby SETSIZE (at one point I had sockets surviving program termination that remained ESTABLISHED)
  1. Ruby SETSIZE > EM SETSIZE
• segfault

have you tested it with rubyinstaller 1.9.3-p194 ?
i'm having some problems with it... see #319.

@stakach Since 8840d22 solves #319 and could be considered a fix this is beyond the scope of just this PR think you could extract it into a new one?

Well the aim of this pull request was to improve windows support on eventmachine.

@tmm1 is there any reason we can't merge these changes and create a new windows release?

@raggi maybe you could help?

Note to self: Check if #570 includes this work.

Superseded by #630