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? M Sent from my iPhone On Apr 2, 2008, at 9:06 AM, Pavel Pragin <[EMAIL PROTECTED] > wrote: > > I am sorry I am not sure how turn the header off. Is this in Apache? > thanks > -- > Posted via http://www.ruby-forum.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 -~----------~----~----~----~------~----~------~--~---
