rubyonrailsin

Hi all,

I thought I would introduce a wild idea I had this morning while thinking about multi-site implementations. One reason that I have not tried to use any of the existing multi-site extensions is I want to have really fine grained control over the gems and radiant extensions that are loaded for each site. (If there is a way to control this with the existing multi-site extensions, then please let me know how.)

Radiant itself already handles controlling the extensions and gems loaded during startup. What if we added another layer to that logic, and created an extension that knows how to do the same thing but for site? So basically, Radiant core would just load the multi-site extension, and then every site would be what we now consider a Radiant instance. (If that makes any sense.)

Another way to imagine this is to think about the multi-site functionality becoming the parent of Radiant core, instead of trying to fit a multi-site extension inside of Radiant (either directly in core or through extensions).

I am not all that familiar with the core code-base, yet, so I am not sure if this is possible, but I thought I would pontificate and see what others think.

Now that I have typed all of that out, though. It is starting to sound to me like these features might be best implemented as a rack middleware that Radiant can play nicely with. The middleware would own just sites and users, but radiant would own pages, layout, snippets, etc...

I imagine that this would be useful to others in the Ruby community (if it has not already been done), and it would make it possible to have some sites that run rails apps, like radiant, others that are simple sinatra apps, and others that are instances of any other rack-based web solution.

Thoughts?
-Scott

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/