To begin with, I have worked with many, many clients for whom
scalability is a core concern. All of them use sticky sessions (with
a backup server).
Second, Tapestry is designed to store a pretty minimal amount of
information in the HttpSession, in that it tends to store simple,
immutable object
Hi,
I have been evaluating several Java Web frameworks. Regarding Tapestry
5, I like very much its POJO, non-intrusive programming model.
I am interested in knowing how well Tapestry 5 applications perform on a
clustered environment. Like most Java Web frameworks, Tapestry 5 handles
action r
Tapestry doesn't generate 2 requests all the time,
only for action requests, but even then only for some actions.
You are not forced to store you database objects in the session,
you can store Object id only, you your self will be responsible for scaling
issues, but tapestry will definitely give
Hi,
I have been evaluating several Java Web frameworks. Regarding Tapestry
5, I like very much its POJO, non-intrusive programming model.
I am interested in knowing how well Tapestry 5 applications perform on a
clustered environment. Like most Java Web frameworks, Tapestry 5 handles
action r
