uPortal developers, Has anyone given thought to what it would look like to, at the framework layer, make all the portlet markup render down to the browser asynchronously?
Individual portlets have been developed to asynchronously render their content, first rendering a loading... experience and then replacing that with content once loaded. I think the email preview portlet or so does this. But I'm wondering about implementing that generically at the framework level. Instead of interpolating dynamic portlet content in the theme transform and having that HTML all cooked server side and fed down to the browser, instead generate the AJAXy placeholders that call back to the server to get their portlet's markup when it's ready. (I imagine if I understood Web Sockets I'd want to use them for some aspect of this and that would be better in some way.) Obviously, there are *better* experiences to be had by designing AJAX usages within individual units of content. Would need a way to opt portlets into or out of this magic handling. But still. Is there any potential in this idea? Anyone tried this? Kind regards, Andrew -- 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
