Thank you, Dan. I appreciate the feedback and info! Ken
On Apr 7, 2009, at 7:58 AM, Dan Simpson wrote: > From what I can tell, engines have a long way to go. They still > serve a good purpose as is, but have several shortcomings. > > What they can do: > Define application files (app dir) > Define routes > > ... and that seems to be it for now. Migrations, plugins, and > static files need to be synced via a rake task. App requirements > that you want to define in environment.rb, well, you can probably do > it with some IO, but there is no support out of the box for it. > > So to sum it up, it's good but immature. > > --Dan > > > On Tue, Apr 7, 2009 at 7:34 AM, Ken Hudson <[email protected] > > wrote: > Now that support for the engine plugin has been incorporated into > Rails 2.3, I'm very interested in taking advantage of this > functionality. Specifically, I would like to be able to embed one > rails application within another. I think this would have > tremendous productivity benefits down the road. However, I'm > curious how well this actually works in practice and what the real- > world limits are. Do Engines in Rails 2.3 work well? Practically > speaking, how many apps can be embedded in another app? (I'm not > talking about theoretical limits but more real-world practical > limits.) Also, what is the best way to handle authorization and > authentication? Finally, would I be better off waiting for the Merb > Slices functionality to be added to Rails 3 or would starting with > Engines now put me in a "better" position when Rails 3 is released? > Answers to these questions as well as any other thoughts or > experiences would be much appreciated. > > Thanks, Ken > > > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
