On Thu, Jan 8, 2009 at 4:42 PM, johnswolter <[email protected]> wrote:
> > One suggestion I've been thinking about is to make the router into an > easily replaceable plug-in, if you will. I can imagine all kinds of > reasons to have special purpose and feature routers. I'd love to hear them. Honestly, I can't think of any offhand that would trump a flexible enough router. Maybe this plug-in idea could be for the whole product. Every core > part of Rails would be a plug-in. Rails then would be defined as a > structure frame.... [snip] > A site architecture, for example, could be designed using Amazon Web > Services virtual servers creating execution nodes on demand with > distributed Rails loosely-coupled plug-in parts running and > communicating as needed. It seems to me that you're still going to need some sort of communication between those nodes. We already have a means of communication for web apps -- HTTP. And we already have a way to scale Rails on EC2 -- put a load balancer (nginx) in front of it, and let each node run a webserver. I would love to see Rails be more modular, but I'd rather see that at the activesupport level -- for example, I need inflection in a library I'm writing, which is neither Rails nor Merb. My two best choices are activesupport or extlib, both of which include WAY more than I need. Other than that, I suppose I could use Sequel, which is even more stuff I'm not using. Inflection should be its own gem. So should time intervals (5.days.ago). In particular, anything that messes with core Ruby classes, I'd like to be able to use without pulling in everything else that messes with core Ruby classes. But the other stuff in core, like the router... Any router is going to be tightly bound to a controller model, unless it's something without a controller, like Sinatra. What is gained by making them pluggable? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
