Sure ! :)
I think JCR is a great fit-all standard. And OCM can be a great RAD
tool (and this is why I started trying JackRabbit instead of SQL
databases). So let's use whatever best fits our needs.
But what's great with David's model is that, in its current form, it
seems to apply well to both cases.
Frank
Le 09-11-16 à 14:17, Bertrand Delacretaz a écrit :
2009/11/16 François Cassistat <[email protected]>:
...I see this from a RAD and object database perspective.
OCM provides a sort of CRUD interface on objects. Defining an
object is
simple and fast, then you specify the location and begin using it.
No need
to worry about structures and everything. Maybe OCM have
limitations and is
not optimal, but software is written fast and easier to be changed.
This is
perfect for iterative development where changes are likely to be
asked...
Thanks for sharing your point of view, and if that works for you we
shouldn't say you're doing the wrong thing!
I'm coming from a content management point of view where JCR fits very
nicely in the picture as is, with (IMHO) no need for extra layers. But
your example shows that depending on your environment and goals,
there's space for OCM.
-Bertrand
