portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5664] New: - Pre-loading portlets
Date Wed, 02 Jan 2002 19:49:20 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5664>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5664

Pre-loading portlets

           Summary: Pre-loading portlets
           Product: Jetspeed
           Version: 1.3a3-dev / CVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Registry
        AssignedTo: jetspeed-dev@jakarta.apache.org
        ReportedBy: mark_orciuch@ngsltd.com


It would be useful to a functionality to pre-load all portlets in registry at 
startup for performance reasons. As discussed with Paul Spencer:

"A enhancement would be to add a "_preload_default_content".  Thus if a 
user altered the default portlet configuration, their portlet would NOT 
be pre-loaded.  Portlets that generate user specific content would NOT 
be pre-loadable."

Additional details per Paul Spencer:

"My initial thought was setting this only in the <portlet-entry>, but also 
having a configurable default value set in JR.p is a good idea."

"The portlet would be preloaded into cache.  It will be up to the portlet 
to load it's content."

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


Mime
View raw message