Rails 3.0 and Ramaze

I just saw this ...

http://arstechnica.com/open-source/news/2010/08/ruby-on-rails-30-released.ars?goback=.gde_22413_member_28460794

and it includes this line "In 3.0, this is extended to the router which lets you run any Rack-compatible application within Rails—Sinatra, for example.". I assume that this would hold true for Ramaze also, but I'm not sure what it really means. Why would you include a Sinatra or Ramaze application within Rails?

Any ideas?

--
Scott
http://steamcode.blogspot.com/

For when you build fairly complete sub-systems....like an
authentication engine user account management backend, or file manager
facility or commenting facility, or credit card processing module,
etc. You can build the sub-system once, yet roll it out under more
than one deployment as a sub-component of a larger deployment.

Michael

> --
> You received this message because you are subscribed to the Google Groups
> "Ramaze" 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/ramaze?hl=en.
>

--
http://codeconnoisseur.org

Michael,

Thanks, that makes sense. I guess I'm not convinced it'll be used a lot as it seems like most people pick a framework and stick with it, but I can see where it might be useful for specific cases.

ScottScott
http://steamcode.blogspot.com/