+1 for the change.
We commonly see situations where new portlet developers accept the
defaults, get a timeout the first time the portlet they're working on
renders, then get confused and chase phantoms for a few hours that could
have been productive. (It's easy to go more than 5000 ms in
"bootstraping" for a portlet with even modest complexity.)
drew
On 08/28/2013 12:08 PM, James Wennmacher 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?
--
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
