Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: domain of smithh032772@gmail.com
 designates 209.85.212.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1371658506352-115108.post@n7.nabble.com>
References: 
 <CAGV1rDJ9gHNzOrZf+2SPiDX-dMsF5vVngbeSqkiUW_=C3s3MnA@mail.gmail.com>
	<CAAuOd=ULgNhpebZQbMUf168X2xHiC1rNWpjrrbfPvcFLKWRH=w@mail.gmail.com>
	<CAGV1rD+Osf-sxYSNYVb832JXoSc+MCgxqeMDROGYyLbRX44mEA@mail.gmail.com>
	<CAAuOd=VwX2hnoNZcSKxjYkcQf6q3gmge37PX+jaL4PttXOZT3g@mail.gmail.com>
	<CAGV1rDJvimnU1q-y28nHvtZMW5uPcygmj6zwZ9QbbgPOP_XNxA@mail.gmail.com>
	<512771B0.6040908@senat.fr>
	<CABujnVdAHy2pjZxAM+QzZeQauiFQ_cDButhhi6f1oQ_039g7cw@mail.gmail.com>
	<1371658506352-115108.post@n7.nabble.com>
Date: Wed, 19 Jun 2013 12:47:32 -0400
Message-ID: 
 <CAGV1rDLqZ3JGhLWq03Ozo+YjTVWS6qRH=65as8-xp0-Y2P+eHQ@mail.gmail.com>
Subject: Re: Add 'Stateless JSF' to MyFaces Core? Is it really necessary?
From: "Howard W. Smith, Jr." <smithh032772@gmail.com>
To: MyFaces Discussion <users@myfaces.apache.org>
Content-Type: multipart/alternative; boundary=001a11c338d00a52e304df84960d

--001a11c338d00a52e304df84960d
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 19, 2013 at 12:15 PM, nabbling1138 <newton.whitman@gmail.com>wrote:

>
> It has everything to do with avoiding your users experiencing a ViewExpired
> state exception on a trivial form such as a login.
>

ViewExpiredExceptions are 'no' longer a concern of mine since I am using
OmniFaces restoreView component.

Also, for my home-grown/custom security-n-session-management
implementation, my login page access @SessionScoped userBean.login, but
since I've been hearing others advise to use @RequestScoped more than
@SessionScoped (as much as possible), I am considering changing my
implementation, so the login page will access @RequestScoped user bean
instead of @SessionScoped. I am quite sure that that will allow my login
page to sufficiently/theoretically avoid View Expired exception. I plan to
try this...when I feel like it, or have bandwidth to do so. :)


> It is non-intuitive for users to get errors (however you have handled them)
> on simple forms when they went to lunch and came back.
>

Agreed. Thank God for OmniFaces restoreView component!


>
> Example: Imagine going to your favorite shopping web site. You get
> interrupted and come back in 30 min - you go to run a search and you get
> redirected to a friendly but annoying web page or maybe they force you back
> to a page but you loose everything you typed. Awful customer experience!
>

Good point/example. I felt the same way while developing my current
security/session-management implementation (over time). My app is
definitely no 'shopping web site' and endusers of my app are very
understanding of a 15-minute-session-timeout limit for security purposes,
and I would 'only' assume shopping web sites would require/utilize
@RequestScoped beans anyway. Take for instance Google or MSN.com search
engines... Google loves 'history' (and so do I), @RequestScoped bean
accepts the input of the enduser, and can update 'search history',
accordingly when user 'come back in 30 min' to his search page and press
Enter...to begin the search. :)

Surely, not rocket science.


>
>
> --
> View this message in context:
> http://myfaces.10567.n7.nabble.com/Add-Stateless-JSF-to-MyFaces-Core-Is-it-really-necessary-tp114248p115108.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>

--001a11c338d00a52e304df84960d--