On 3 sep, 21:01, Aldric Giacomoni <[email protected]> wrote: > Well, just remember that Rails is a web framework, and Ruby is (as has > been mentioned) an interpreted language. > If speed matters, then you need to go as low in the language hierarchy > as possible. And usually when you talk about going low, you mean C... As > I was reminded here, though, bits of Ruby gems are written in C, > precisely for speed reasons :)
That helps :) > > And if every millisecond counts, then yes, you probably want to control > everything, and that means email is probably also the wrong way to go. > You'll probably want to send your own messages through your own > interface. I did not test this and I can be wrong, but it may be faster > to just send one TCP packet with a code which gets translated to a real > message when it gets to the recipient. Again .. Speed vs. Flexibility :) We don't control the recipient and we have to send an e-mail. It might change, but it won't for the forseeable future. > > Good luck, and remember to share what you learned.. If you can't share > the code ;-) I will share what I can share, but if I don't use Rails, I probably won't be sharing it here ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
