Running JSF in stateless mode (0 cost to maintain state)

I recently ran into the rugged JSF extension (Mojarra) developed by Rudi, which claims to provide significant performance improvements with even lower memory / processor costs and reduced latency, with 0 memory overhead to save state, and also say goodbye to obsolete views (Postbacks will always work). All this seems very impressive!

I am a naive JSF developer involved in projects using JSF for a high-performance Internet application. I wanted to know what I should worry about before going to stateless pages in JSF. I have already tested my application using this stateless project (most of them work without any changes), but I wanted to know what I should think about before moving.

I know that there is already a proposal to include a stateless status function in the official JSF specifications, but I'm not sure how long this should take, and until then this JSF extension could help me a lot.

Also, is there any of them, also using the Stateless JSF project in production environments?

-

Update: For those who work with Myfaces, the stateless extension was redefined by Thomas Andrashko and was proposed to be added to the main Myfaces project .

Using JSF 2.1.3 with stand-alone extension and priming 3.4 Snapshot.