> -----Original Message----- > From: Ralph Goers [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 01, 2004 3:32 PM > To: [EMAIL PROTECTED] > Subject: Re: [portal] Need for CachingPortletAdapter > > > ĎURDINA Michal wrote: > > >Hi, > >currently provided PortletAdapter does not offer caching > ability for JSR168 portlets. I really need caching for > portlets and I wanted to implement this feature as new > CachingPortletAdapter. > > > >Having looked at URICopletAdapter and > CachingURICopletAdapter the caching implmentation for coplets > is pretty simple. > > > >CachingURICopletAdapter relies on these principles: > > - coplet content is XML > > - coplet content it is cached/emited in the generator of > portal generating pipeline > > - links are cached untranslated and the link translation > occurs in the transformer that follows generator > > > >PortletAdapter relies on these principles: > > - portlet content is not XML (however it is often XHTML) > > - portlet content is emited in serializer of portal > generating pipeline > > - links are translated in the portlet generation and are > part of portlet content > > > >Main issue I see in implementing CachingPortletAdapter is > "link translation". > > 1.) links that are sent to browser are valid only for the > next request > > 2.) translated links are part of generated content > > 3.) portlet content cannot be cached since its links will > not be valid after next request > > > > > If you use PageLabels the above is not true. Events are valid until > they are regenerated on the next request to that page label. > > >Has anyone been thinking about the caching of content for > JSR168 portlets? I would be happy if we could come to common > solution that could be consequently implemented. > > > > > No, I haven't been thinking of it, but it seems like it would > be a good > thing. I'd welcome a proposal and/or code. > > >Michal > > > > > Ralph > >
Thanx! Your PageLabels seem like great enhancement to the portal engine. Need to look closer but seems like caching of portlet content will be breeze with pagelinks in use. But there is one issue remaining. I am afraid that links don't work on first portal page in samples. Seems like pagelinks won't work on pages with no tabs. Did you encounter same behaviour? Michal
