portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor" <da...@bluesunrise.com>
Subject RE: Portlet Instances
Date Tue, 06 Aug 2002 16:39:15 GMT
Portlets are not thrown away after aggregation.
Portlets remain in memory for as long as they are configured to.
The part that could be optimized is the creation of the transient portlet
sets (and now wrappers) with every request....

A portlet instance is the runtime view of a portlet with its set of
configuration and customization attributes. This runtime pair (the portlet
object and attributes - from the psml page and configuration) define an

> -----Original Message-----
> From: Wimmer, Matthias [mailto:matthias.wimmer@scr.siemens.com]
> Sent: Tuesday, August 06, 2002 8:41 AM
> To: 'Jetspeed Developers List'
> Subject: Portlet Instances
> Hello,
> I am just figuring out the difference between "Portlet",
> "Concrete Portlet",
> "Concrete Portlet Instance" and "User Portlet Instance". This is how IBM
> calls these different aspects of portlets. How do you call it in the
> Jetspeed world?
> When a page is aggregated in Jetspeed each portlet is instantiated and the
> getContent method is being called. After that everything is
> thrown away. Why
> don't you create the portlets when a user logs in and keep this tree for
> further use.
> Is there any issue that I am not aware of? Is it the memory
> occupancy? Is it
> a good way to deal with missing log off operations of the users?
> I am very obliged to your kind response.
> Matthias Wimmer
> --
> To unsubscribe, e-mail:
> <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:

To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>

View raw message