> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Rimov
> > Sent: Monday, October 30, 2000 5:19 PM
> > To: [EMAIL PROTECTED]
> > Subject: Portlet API
> >
> > I'm very much for defining a Portlet and Portlet Container API to
> > standardize portlets. Everybody already is "cloning" the term
> > Portlet. But what would be a huge service to the developer
> community at
> > large would be to have a standard API to allow portlets
> written for one
> > Portal to be easily switched to another.
> >
Same here since we would not be working on top of Turbine, but be using
Cocoon2 instead. I'm not sure whether a application neutral Portal API would
be a feasible thing, at least a common feature list should be possible.
Since thoughts on content aggregation are surfacing quite a lot on the
Cocoon dev list, and Santiago has been talking with the Cocoon people during
ApacheCon, I believe working across the two apps could be beneficial for
both.
Let me think on this and get back to the list.
</Steven>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
