You're right Andrus. I should have read the documentation first.
Sorry for wasting your time,
Dave
> -----Original Message-----
> From: Andrus Adamchik [mailto:andru..bjectstyle.org]
> Sent: 23 January 2006 18:47
> To: cayenne-use..bjectstyle.org
> Subject: Re: Multiple Data Contexts?
>
>
> "DataContext == logical session" point is made in many places in the
> docs, e.g.:
>
> http://objectstyle.org/cayenne/userguide/datactxt/
>
> Still a Wiki page wouldn't hurt. My opinion is that redundancy in the
> documentation is a good thing, unlike redundancy in the code :-)
> Especially, with nested DataContexts coming in to the picture soon.
>
> Andrus
>
>
> On Jan 23, 2006, at 1:33 PM, Cris Daniluk wrote:
>
> > It seems like there's constant confusion on the DataContext
> > cardinality. Do you think it would be worthwhile to create a wiki page
> > illustrating scenarios and corresponding DataContext strategies?
> >
> > Cris
> >
> > On 1/23/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
> >> I second Michael's suggestion of a dedicated DataContext per client
> >> as the first choice, as access stack synchronization is designed to
> >> automatically handle this scenario.
> >>
> >>
> >>> I currently I have a client server architecture. The client is a
> >>> java applet
> >>> which does nothing more than call an api on the server. The server
> >>> then does
> >>> all the database work.
> >>
> >> ...
> >>
> >>> The architecture may well be expanded to have web applications. I'm
> >>> not
> >>> entirely sure about the architecture for this part at the moment.
> >>
> >> When you do that make sure you check Remote Object Persistence
> >> features:
> >>
> >> http://objectstyle.org/confluence/display/CAY/Remote+Object
> >> +Persistence
> >>
> >> This lets you keep a rich client with Cayenne context on the client
> >> side, and deploy the server part as a web service.
> >>
> >> Andrus
> >>
> >
>
This archive was generated by hypermail 2.0.0 : Tue Jan 24 2006 - 04:19:47 EST