Mark, Mark Orciuch wrote:
> Paul, > > I was not aware that portlets are cached that way. I guess it will make it a > bit tricky. Just few more questions: > > - Will "_preload_default_content" be an entry in jr.props? Or portlet config > attribute? Hopefully, the first one. 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. > - Will pre-loading involve placing the portlet in portlet cache or just > caching the portlet URL? Hopefully, the first one. The portlet would be preloaded into cache. It will be up to the portlet to load it's content. > - What is a portlet that generates user specific content - one that has a > customizer attached to it? Any RSS or WebPagePortlet will generate content using parameters in the PSML. I am sure their are others. I an not aware of a portlet that utilizes user information in it content generation. An example of this is an email client. > - Would it be simple enough to add API for "manual" re-loading of a portlet > (or all instances of the same portlet customized in variety of ways)? Right > now, I have to remove it directly from GlobalCache to achieve this. > The GlobalCache is where this need to be done. As a part of reworking the caching, I am looking into an "admin" function that will remove cached entries. > Other than that, it's definitely a usable enhancement and I'll log it in > Bugzilla. Thanks! > > Best regards, > > Mark C. Orciuch > Next Generation Solutions, Ltd. > Voice: 219-365-0691 > e-Mail: [EMAIL PROTECTED] > web: http://www.ngsltd.com > > Paul Spencer -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
