I'm sure Eric meant 'stateful' instead of 'stateless'.
On 11/1/05, Borut Bolčina <[EMAIL PROTECTED]> wrote:
>
> Hi, you got me a bit confused here. See below.
>
>
> > For stateless apps, each individual user has their own DataContext in
> > the Visit object.
>
> Isn't visit (ASO session) the very
Hi, you got me a bit confused here. See below.
Eric Schneider wrote:
Borut,
I've always stuck to the simplest approach. If I'm dealing with a
completely stateless application, I share one DataContext for all
users (in T4 as a hivemind singleton).
So each request from browser (user) c
Eric Schneider wrote:
Borut,
I've always stuck to the simplest approach. If I'm dealing with a
completely stateless application, I share one DataContext for all users
(in T4 as a hivemind singleton). For stateless apps, each individual
user has their own DataContext in the Visit object.
Borut,
I've always stuck to the simplest approach. If I'm dealing with a
completely stateless application, I share one DataContext for all
users (in T4 as a hivemind singleton). For stateless apps, each
individual user has their own DataContext in the Visit object. I
haven't used the
Hi,
I searched through the archives and read all that I could about
integrating Cayenne with Tapestry. The latest thread "Tapestry, Cayenne
and Squeezer" was informative, especially Filip's post which is on wiki
also. All other posts were a bit out of date I think dealing with T3.
Although re
