The way I see it, the ideal productization would be much like engines,
but on the other side of the application–in a way, engines that
override the application. That’s why I thought to look at engines. I
imagine this would be a new plugin, but I figured a lot of it could be
based on engines code.
I suppose an alternative would be to make the application that would
be productized an engine that depended on other engines. Each instance
would be their own application. This seems like it could work. All the
other engines can be started in the app engine. App specific configs
can be in the app engine… hmm, sounding better the more I type.
I guess that leaves one thing… routes. Can we figure out a clever
way to solve the routes issue? What if engines could draw their own
routes… then in the application route map we’d say something like
Engines.route :my_engine, map or even Engines.route :all, map, which
would pass the map object to engines to apply connections to.
On 3/4/06, James A. email@example.com wrote:
‘productised’ applications to have selective access to various
and get productization working again. Anybody have any ideas on how I