+1 for a sensible improvement to the defaults that will serve many adopters well.
I agree that longer-running processes would do well to be implemented in AJAX. [1] bonus points for revving the documentation / readme / release notes / administrative UI to document the new timeout and the tradeoffs involved in setting it. [1]: Crazy idea: what if the framework became able to just-in-time AJAX-ify longer-running portlets to give them more time to finish rendering? As in, the behavior of the timeout/error portlet would be to render down an AJAX handler that would recheck with the portal to pull down the portlet content once available, rendering a "Loading..." message in the meantime and even replacing that with an error message when *that* times out? This crazy idea might be better than AJAX-ifying all portlets in that portlets that render fast enough don't need to be handled via AJAX and can just have their markup directly included. On Wed, Aug 28, 2013 at 3:08 PM, James Wennmacher <[email protected]>wrote: > I propose we change the portal's default render timeout from 5000ms to > 20000ms. There are portlets that tend to take long time (such as email > preview) or custom portlets connecting to back end systems where 5000ms is > sometimes too short a time. > > I think the user experience in general would be better to have a longer > default so: > - The portal doesn't display an unpleasant message to the user for > longer-running scenarios > - The portal is more tolerant of operational issues such as uPortal or > dependent systems running a bit slow > - Longer-running processes should typically use ajax requests to obtain > the data for a better user experience, so the urgent user response is less > important in these situations since the entire UI is not impacted > > This would affect new portlets that are created via the UI (or imported > without a timeout value I believe) but not existing portlet instances. > > Thoughts? > -- > James Wennmacher > Unicon > 480.558.2420 > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/**display/JSG/uportal-dev<http://www.ja-sig.org/wiki/display/JSG/uportal-dev> > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
