[Grok-dev] megrok.rdb feedback
faassen at startifact.com
Tue Sep 16 07:33:01 EDT 2008
Lennart Regebro wrote:
> On Mon, Sep 15, 2008 at 19:27, Lennart Regebro <regebro at gmail.com> wrote:
>> What I haven't looked at yet
> Oh, and making Models which is storage-Agnostic is an interesting
> topic for the future too. ;) I want that.
Not a goal of megrok.rdb. I see people talking about wanting this once
every while, but I don't see the point of the exercise myself. If you
are storage-agnostic, this means you can't use the strong points of a
particular storage in your code, meaning you lose the benefits...
> I guess that means a sort of field system which wraps whatever fields
> you are actually using. But that's speculation for now.
> I would love to see a Grok CMS that could store it's data wherever. :)
I think the ZODB is quite nice in allowing different storage backends,
but that's not what you're talking about.
I think it is possible to build a CMS that at least allowed different
kinds of content objects to be stored separately. I can even envision
that in particular use cases you have multiple implementations of a
content object, that each store data differently, and a configurable
utility that is a factory for these objects. There needs to be a strong
use case for the latter scenario, though. I don't see much point in
allowing a single object to store its data wherever, however.
More information about the Grok-dev