SEMF has a relationship to Portlet just because they both provide pluggable user interface components.
Anyway the primary target of SEMF and Portlet are different. As portlet try to provide a standard API to communicate between portals in different sites, SEMF is not intend to interoperable with some other implementations. as SEMF is unique:!
Primary Target of providing little web based windows which are analogue to portlet is just allow the users to provide different ways of representing data which is stored in a database.
Well. SEMF is more towards how we represent a given kind of data rather than how it would be processed or how it would be interoperate..
Efficiency is a main requirement of SEMF. We found most of the implementations of Portlets are very heavy. They used to generate the code at runtime which is a big bottleneck in performance. Our approach is to generate the code at design time and publish the generated code which have very little processing to do at runtime.
So it is very little that we can follow from Portlet in here. So we should write our own portlet engine.
Subscribe to:
Post Comments (Atom)
1 comment:
Here are the points we didn't go for portlets.
1. Portlets are heavy-weights. We are developing a light-weight engine.
2. Portlets generate code on request. We generate code initially and serve the pre-generated code for the performance.
3. We already have a design. Why we bother about Portlets anymore.:)
Post a Comment