jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From paksegu <paks...@yahoo.com>
Subject Re: architecture/design of content-centric applications
Date Tue, 03 Jun 2008 03:34:11 GMT
The design of your application depends on your business and user requirements, and this as&nbsp;
will follow application design methodology based on&nbsp;goals, want are you trying to

Ransford Segu-Baffoe



--- On Mon, 6/2/08, Florian Holeczek &lt;florian@holeczek.de&gt; wrote:

From: Florian Holeczek &lt;florian@holeczek.de&gt;
Subject: Re: architecture/design of content-centric applications
To: "Alexander Klimetschek" &lt;users@jackrabbit.apache.org&gt;
Date: Monday, June 2, 2008, 9:27 AM

Hi Alex,

first of all, thanks for your quick response, which gives a nice
I already know the collection "David's Model" and tips like
nt:unstructured for being more flexible.

However, the things you've pointed out are all related to designing
the _content model_. What I'd like to discuss is the "other
side", the
design of an _application_ which uses this content model.


Ursprüngliche Nachricht vom 02.06.2008 um 15:18:
&gt; The classic starting point is David Nüscheler's (JCR spec lead)
&gt; content-modeling guide:

&gt; http://wiki.apache.org/jackrabbit/DavidsModel

&gt; You should design the data model not based on the application code,
&gt; but from a content standpoint: what belongs together, what is
&gt; read/written together most of the time and how can it be organized
&gt; effectively. The latter can always be verified by how easy it is to
&gt; browse through the content tree as a human. And the hierarchical data
&gt; model (together with less-strict typing, eg. nt:unstructured) gives
&gt; you freedom to change the model later (eg. introduce another entity,
&gt; ie. folder) - you are not forced to design the perfect model up-front,
&gt; as you are more-or-less forced with relational database schemas.

&gt; Regards,
&gt; Alex

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message