EP2005 &gt; CPS Portlets : architecture overview<br/><br/>Julien Anguenot &lt;ja@nuxeo.com&gt;<br/>29 Juin  2005<br/><br/><br/>OUTLINE<br/><br/>    <br/><br/>History Framework orthogonality CPSPortlet architecture Cache and performances Summary<br/><br/>2<br/><br/><br/>History<br/> <br/><br/>CMF main_template and macros CPSBoxes CPS-3.0 -&gt; 3.2<br/>  <br/><br/>macro based system sucks ! a mess to maintain (pb of skins overrides) no need to reinvent the wheel all the time. CPS / EPR5 sprint in Paris 2004 CPS3 / CPSSkins integration New design ! major refactoring Chalmers / Nuxeo development See Jean-Marc's presentation<br/>3<br/><br/><br/><br/>CPSPortlets<br/>  <br/><br/><br/><br/>CPSSkins / CPSPortlets<br/> <br/><br/><br/>0rthogonality<br/><br/><br/>CPSSchemas based<br/><br/><br/>reuse of schemas / layouts / vocabularies in between documents, directories and portlets<br/><br/> <br/><br/><br/><br/>Unification of the CPS3 architecture Only one concept to learn now to integrate on CPS. PlonePortlets uses the same paradigm with AT.<br/><br/>4<br/><br/><br/>CPS Portlet<br/><br/><br/>Cope only with portlet content<br/><br/><br/>CPSSkins will cope with portlet decorations (JSR168)<br/><br/>  <br/><br/> <br/><br/>Content type object CPSDocument base class (FTI) Specific API extensions (such as RAM Cache) Schema-based Could be even workflowed ;)<br/><br/>5<br/><br/><br/>Portlet architecture overview<br/><br/>6<br/><br/><br/>Portlets repository<br/><br/><br/>Central repository (portal_cpsportlets)<br/> <br/><br/><br/><br/>visible in all sub-folder by default has a tendency to increase in the tree basement displayed inside the theme overrides (unless explictly disallowed) placeful configuration displayed inside the theme's slots rulez<br/><br/><br/><br/>Local portlet containers<br/>   <br/><br/><br/><br/>Security and portlet management delegation in place.<br/>7<br/><br/><br/>Cache for performances<br/><br/><br/>RAM cache integrated on portlets<br/>  <br/><br/><br/><br/>stored wihin dicts {(index,...), value), ...} tuple index represents the cached object index is composed by (object_path, attr1, attr2, ...., attrn) see cache parameters index is a way to identify the object's context setEntry(), getEntry(), deleteEntry() invalidate() getStats(), getReport(), getSize(), getLastCleanup()<br/><br/><br/><br/>C a ch e<br/>  <br/><br/>  <br/><br/>Lazy invalidation Invalidation event service based Decrease seriously rendering time<br/><br/>8<br/><br/><br/>Summary<br/><br/><br/>   <br/><br/>Major performance improvements with the caches Sexy interface ;) Enhance user experience Architecture unification For documentation see<br/><br/><br/>http://svn.nuxeo.org/pub/CPSPortlets/trunk/d oc/<br/><br/>9