Improved thread safety in remote fetcher

[anibali]

The current process of caching connections in @connections causes problems across multiple threads, due to unexpected socket closing. By adding the current thread's ID to cache keys this problem may be avoided without affecting single-threaded applications.

[jbarnette]

Thanks, will you please open up a ticket pointing here in the RubyGems tracker?

http://rubyforge.org/tracker/?group_id=126

[qrush]

Just curious, where is the RemoteFetcher being used in a multi-thread environment? Not saying that we shouldn't support it..but curious as to how this bug was found :)

[anibali]

I stumbled upon this issue through gem-dependent (see https://github.com/grosser/gem-dependent/issues/issue/3). The problem is currently circumvented by spawning multiple processes, which is very wasteful of resources in comparison to threads.

[zenspider]

applied