thanks eelco i get your point. deciding what to sacrifice in design whether memory or cpu/db traffic is always some challenge for most developers but if I dont want my DB crying then its probably time to buy more RAM
On 10/16/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > Does this approach have any significant improvement over the former? and > > what could be the cons > > Like Alex said, look at LoadableDetachableModel for instance. You > don't have to discard right away; just do at at the end of the > request. It's what detachable is for. > > Pro detaching: less memory consumption per session, and you can avoid > lazy loading problems when you use e.g. Hibernate. Con: more database > traffic (if you don't cache these objects) and cpu usage (though very > very minimal). In general a pro is also that your objects are always > fresh. A general con when working in forms can be that you have to > persist changes right away or you'll lose them with the reload. > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
