Also take a look at nested DataContexts. In desktop apps they are
much more useful than in web apps, e.g. for things like nested
dialogs, where you need to save or cancel dialog input without saving
to the database.
Andrus
On Nov 15, 2006, at 8:53 AM, Michael Gentry wrote:
> Back in the old days, when I used to do NeXTstep/EOF development, this
> was pretty much how we did it. EOF (Cayenne) was used to access the
> DB and it worked well. As far as things to pay attention to ... I'd
> use optimistic locking (which I'd recommend for a web-based
> application, too) and refresh data you think needs to be refreshed.
> Refreshing data is really an application/workflow specific detail, so
> it is hard to generalize. Some things are obvious, like you can cache
> the State and Zip Code tables, for example. Other things you'll have
> to evaluate depending on your situation. It hardly ever hurts to
> refresh data from common queries, unless the query is really slow.
>
> Not sure if that helped ...
>
> /dev/mrg
>
>
> On 11/15/06, Tomi NA <hefes..mail.com> wrote:
>> I'm developing a rich client application using cayenne as the ORM.
>> So far I've used cayenne in web applications only, and as far as I
>> can
>> tell, it's the dominant use case.
>> Seeing how rich clients arround a db server are a very different
>> story
>> (cayenne running in different JVMs on different machines, rather than
>> in one JVM on the server), is there anything I should be paying
>> special attention to, especially along the lines of caching data and
>> locking mechanisms?
>>
>> TIA,
>> t.n.a.
>>
>
This archive was generated by hypermail 2.0.0 : Wed Nov 15 2006 - 09:54:45 EST