<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
On Thu, 2006-07-27 at 13:45 -0400, Daniel Salama wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#000000">Robert, I understand your approach. However, I don't know if using </FONT></TT><BR>
<TT><FONT COLOR="#000000">DCM at my beginner's stage may be more complicated. I also think </FONT></TT><BR>
<TT><FONT COLOR="#000000">that, although RAM is getting cheaper every day, there are just </FONT></TT><BR>
<TT><FONT COLOR="#000000">physical limitations that machines have. I'm looking over my </FONT></TT><BR>
<TT><FONT COLOR="#000000">application's data and it's not that bad, considering that after 2 </FONT></TT><BR>
<TT><FONT COLOR="#000000">years worth of data, I'm using approximately 1GB of hard drive space. </FONT></TT><BR>
<TT><FONT COLOR="#000000">So, independently of that, and if I understood you correctly, when </FONT></TT><BR>
<TT><FONT COLOR="#000000">I'm abstracting and accessing my model through the director, it </FONT></TT><BR>
<TT><FONT COLOR="#000000">sounds to me that either I persist all on storage or in cache (for </FONT></TT><BR>
<TT><FONT COLOR="#000000">each director). If I choose cache, then I have to manually write code </FONT></TT><BR>
<TT><FONT COLOR="#000000">to persist changes, instead of it being "automatic".</FONT></TT><BR>
</BLOCKQUOTE>
Yes, you have understood the issues exactly.<BR>
<BR>
A reasonable way to work is to use completely persistent objects and see how the performance <BR>
is for you --- LISP and elephant support this kind of rapid prototyping extremely well. I may be <BR>
a bit old-fashioned---but I often find that I end up having to take explicit control of the write-back<BR>
policy in any case, and I personally never find having to remember when to write things a burden,<BR>
since they are almost always part of a "business rule", if your using a 3-tiered application.<BR>
<BR>
On the other hand, you can follow your plan based on Ian's idea, and similar layer on secondary <BR>
indexes once prototyping shows that you need them.
</BODY>
</HTML>