On Wed, Apr 2, 2008 at 9:43 AM, Marc Byrd <[EMAIL PROTECTED]> wrote: > > I for one am glad rails has avoided threading, but find the multi- > mongrel approach a little lacking. As a twisted python user, I find > the asynch approach far superior to threading for network tasks. > Twisted apps I have built handle tens of thousands of requests per > second. > > An example in ruby would be resizing an image stored on s3 - the > twisted way is to launch the http get, then add a callback that gets > invoked when the download is complete, thus allowing the server to > serve many other requests in the meantime. > > Anyone else thinking in this direction?
I remember Twisted Python being really cool back in my Python days (even met a committer at a lan party one, heh). I think the thing to do would be to create a similar ruby web server that supports the Rack interface. That's the approach taken with other projects like Thin and Ebb: both of which look really cool. -- Rick Olson http://lighthouseapp.com http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
