incubator-adffaces-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Winer" <>
Subject Re: Combining Trinidad and Tomahawk in single web app
Date Sun, 20 Aug 2006 02:19:29 GMT
I should point out that the MyFaces (not Tomahawk, strictly
speaking) state saving algorithm for server-side state saving
without serialization and the Trinidad token-based client-side
state saving mechanism are rather similar.

When you use Trinidad with MyFaces, because of how
things are set up, the only options are MyFaces server-side
and Trinidad client-side.  Trinidad doesn't provide a
server-side version, and overrides the client-side version
entirely (RI or MyFaces).

So, I'd say it doesn't deeply matter - you'll get good
performance either way.  There are some optimizations
in the Trinidad mechanism that are not found in MyFaces,
and one thing I'd like to look at is comparing the two
codebases and either picking one to move forward
with, or merging the two to get the best of both (if
each does have unique advantages).

-- Adam

On 8/19/06, Mikhail Grushinskiy <> wrote:
> To achieve decent performance with Tomahawk state saving has to be set to
> "server" and serialization turned off.
> Trinidad in contrast recommends to use state saving on "client". (due to its
> token-based mechanism).
> State saving is controlled by single parameter which is set for the whole
> web app.
>     <context-param>
>         <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
>         <param-value>client</param-value>
>         <!--param-value>server</param-value-->
>     </context-param>
> How would it be possible to combine Trinidad and Tomahawk in a single web
> app with this restriction?
> Thanks,
> --MG

View raw message