jetspeed  

[VOTE] Portlet API, Results of the Chat

ingo schuster
Wed, 28 Feb 2001 12:48:42 -0800

Hi,

I posted the log of the PortletAPI chat some days ago. As there where no 
responses, I assume that nothing is left to discuss with regard to the 
issues we talked about in this chat. As we (at IBM) a very keen to start 
implementing the new API, I'd like to vote about the point that we seem to 
agree upon. We will of course have to vote on more details, however as soon 
as the core design decisions are clear, we can at least start with the 
implementation.

So I ask you to vote about following points:

Point 1 (output model):
The API will have streams in the base response API, SAX support in a 
sub-interface; compliant portals must implement both interfaces.

Point 2 (content model):
Fragments are the prefered output model for portlets but the portal must 
implement full documents support as the default.
The content model used by a portlet is defined in its portlet descriptor.

My votes are obviously +1 for both.

--------------------------------------

Below are some open questions. We can try to vote on them (just to get a 
feeling of the opinions) and if there is disagreement they'll need to be 
discussed:

1. Should PortletRequest/PortletResponse have methods to access 
ServletRequest/ServletResponse?
2. Should the session object be passed as separate object of the 
Portlet.service() method?
3. Should attributes in PortletRequest and PortletSession be prefixed by 
the portlet container to separate portlet namespaces?
4. Should we stick with the attribute getters/setters from the Servlet API 
or use the DynamicData object consistently across the relevant objects 
(request, session, configuration, user, page)?
5. Do we want to stick with a pre-defined set of capabilities. Preferably 
not, but if the names of capabilities are standardized, how is the portlet 
going to find out whether a particular capability is present?
6. What should be the interface of the user?

--------------------------------------

I updated the java docs in the proposals directory again. I think I'd make 
sense to vote on the API in four parts, voting on part one should be done 
as soon as there is agreement on the above questions:

1) Core: Portlet, PortletRequest, PortletResponse, PortletSession, 
PortletConfig, PortletContext, SaxPortlet/Request/Respone

2) CoreExt 1: PortletLog, DynamicData, PortletWindow, PortletTitle, Client, 
Capability,

3) CoreExt 2: Page, User, PortletMessage, PortletAction

4) Events: Window, Message, Action



ingo.



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?:          [EMAIL PROTECTED]

  • [VOTE] Portlet API, Results of the Chat ingo schuster