Thanks Martin. It will be great news if browse back button works. Do I have to use </redirect> in JSF navigation for this to work properly?
Regards, Yee -----Original Message----- From: Martin Marinschek [mailto:[EMAIL PROTECTED] Sent: Monday, 27 March 2006 3:56 PM To: [EMAIL PROTECTED] Cc: MyFaces Discussion Subject: Re: [SPAM] Re: How to speed up JSF Hi Yee, yes, the number of views in session tells you how many rendered component-view-trees will be stored - so that you can properly use the back button with server side state saving. That's actually no performance issue - it was just in the middle of the performance tuning stuff ;). We recommend not to use session beans - rather use request-scoped beans and something like t:saveState to make sure the beans will be there for the dialog you want to handle. Then you can use the back-button out of the box, and don't have any special needs. If you do want to use session beans - well, then you're having a hard time with the back button ;). regards, Martin On 3/27/06, Yee CN <[EMAIL PROTECTED]> wrote: > Martin, > > What is the meaning of NUMBER_OF_VIEWS_IN_SESSION=20? Is it the last 20 > views rendered? If I set all my beans to be of SESSION scope, will it limit > the size of my session? > > Can I make use of it to implement 'back' functionality - maybe with a phase > listener that logs the pages being visited in a circular stack, and a util > bean with a backAction() that pops the stack? > > Do you think something of this nature will work? > > Thanks > Regards, > Yee > > -----Original Message----- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Monday, 27 March 2006 3:13 PM > To: MyFaces Discussion > Subject: [SPAM] Re: How to speed up JSF > Importance: Low > > use the following settings, and you should have much better > user-interaction: > > <context-param> > <param-name>javax.faces.STATE_SAVING_METHOD</param-name> > <param-value>server</param-value> > <description> > State saving method: "client" or "server" (= default) > See JSF Specification 2.5.2 > </description> > </context-param> > > <context-param> > > <param-name>org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION</param-name> > <param-value>20</param-value> > <description> > Only applicable if state saving method is "server" (= default). > Defines the amount (default = 20) of the latest views are > stored in session. > </description> > </context-param> > > <context-param> > > <param-name>org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</param-name> > <param-value>false</param-value> > <description> > Only applicable if state saving method is "server" (= default). > If true (default) the state will be serialized to a byte > stream before it > is written to the session. > If false the state will not be serialized to a byte stream. > </description> > </context-param> > > <context-param> > > <param-name>org.apache.myfaces.COMPRESS_STATE_IN_SESSION</param-name> > <param-value>false</param-value> > <description> > Only applicable if state saving method is "server" (= > default) and if > org.apache.myfaces.SERIALIZE_STATE_IN_SESSION is true (= > default) > If true (default) the serialized state will be compressed before > it > is written to the session. If false the state will not be > compressed. > </description> > </context-param> > > Apart from that, using facelets over JSPs is supposed to increase your > app speed by 14% (these are unofficial numbers I've heard on these > lists ;) > > regards, > > Martin > > > On 3/27/06, Guillaume Doumenc <[EMAIL PROTECTED]> wrote: > > Hi Yura, > > > > I'm also using MyFaces without JSP and think that JSF rendering is slow.. > > So if someone can complete this info, I will be interested.. > > > > Regards > > > > > > Yura.Tkachenko wrote: > > > > > > > > Hi, > > > > I just finding some ways to speed up JSF. I'm using MyFaces implementation > > and actually I don't like how JSF is rendering it's very slow. I've never > > tried Facelets with MyFaces is it really can speed up work of my > > application? Because I have only little theoretical knowledge about > > Facelets. But on all my JSF pages I actually doesn't use JSP as it, so I > > suppose I have always some time to: compile JSP(only 1 time) + execute jsp > > compiled class. So I think if Facelets miss this step then my application > > will work much faster, am I right? > > > > + Another approach to use AjaxAnywhere with this library server response > > executes much faster, because user requests not all page, only part of it. > > > > Anyone use Facelets+MyFaces+AjaxAnyWhere is it faster for user then only > > MyFaces? > > > > > > > > Thanks, > > > > Yura Tkachenko > > > > Murano Software Kharkov, Ukraine > > > > mailto: [EMAIL PROTECTED] > > > > http://www.muranosoft.com > > > > > > > > > > > > > > -- > > Guillaume Doumenc > > StudioGdo : Maîtrisez votre communication... > > Tél : +33 (0)6 11 95 24 78 > > Courriel : [EMAIL PROTECTED] > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
