Re: Asynchronous HTTP request

< :the previous in number ^ :the list in numerical order > :the next in number P :the previous (in thread) N :the next artilce (have the same parent) |<:the top of this thread >|:the next thread ^ :the parent (reply-to) _:the child (an article replying to this) >:the elder article having the same parent <:the youger article having the same parent ---:split window and show thread lists | :split window (vertically) and show thread lists ~ :close the thread frame .:the index ..:the index of indices

Daniel DeLorme wrote: > I didn't post that code without testing it. If you look at it a bit more > carefully maybe you'll understand how it works. The HTTP request is sent > after the first Fiber#resume but the fiber yields before attempting to > read the response. Oh yes, sorry about that. I'd digested one of the method_missing sections but not the other. It still seems like unnecessary complexity when ruby threads are cheap, but it achieves what you want. -- Posted via http://www.ruby-forum.com/.