Umm... Just like to throw in my two cents... In Rails ActionMailer is a model, it makes no sense. Mailers are just views that can render various formats, so should be a 'unusual' view format like rss or other. I hear that Merb does it this way. Rendering to a different 'output' to the standard webserver. render :action => 'my_email_template', :output => 'email', :send_to => '[email protected]' with filename my_email_template.text.erb and/or my_email_template.html.erb
On Jan 12, 8:32 pm, Michael Klishin <[email protected]> wrote: > On 12.01.2009, at 3:24, MilesTogoe wrote: > > > 1) continue to have webrick (merb now seems to require mongrel and > > mongrel just seems to give us occasional problems) > > Rails is on Rack already, which means perfect web server portability. > > > > > 2) for deployment - run on nginx plus passenger since I hear nginx > > is so > > much faster and less memory intensive than apache and passenger makes > > deployment simple > > How is it a web framework feature? You can deploy using Nginx and > Passenger today. > > > > > 3) convert AR migrations and model files to datamapper - since we're > > not > > changing the data, just the ORM definitions and datamapper migrations > > updates and keeping definitions in the are far superior > > This is possible only in theory: may migrations operate data directly > by using AR models, and contain arbitrary Ruby code. > Tools that make guesses about how to preserve data integrity are > extremely dangerous. > > > > > 4) make datamapper work with has_many - not sure what real advantage > > has_n is aside from a few less characters (maybe easy to just have > > either work) > > has n syntax lets you use ranges to specify cardinality. n means > Infinity. It is not exactly what AR's has_many does. > > Keep in mind DataMapper is a separate project and evolves the way > DataMapper community think is good. > > > > > 5) merb auth and sessions - rails requires a 3rd party auth plugin - > > auth is too important and should be in core and work well with session > > Authentication means many things to many people, > and so far no single solution was considered perfect by Ruby community. > In many years. > hassox rewritten merb auth twice before it started look good enough to > him. > Believe me, when you implement something twice, you really start to > understand > pros and cons. > > To me, plugins are still a proper approach to this sort of > functionality. > > > > > 6) good "how-to" wiki - since there will be likely be many conversion > > questions based on different user needs > > it is likely to be a Rails guide — wikis are polluted by spam and > trolls way too often > > > > > 7) add svg as built-in mime type > > You can add it yourself today, it is a one liner. > > MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
