Steve,
Suggestion: Add a configuration tag to the portlet definition
which specifies whether or not the portlet will produce partial
or full content.
You probably mean the deployment descriptor, not the portlet definition...
Suggestion: Create portlet wrappers for full content stripping
: Re: [vote] Portlet API - Summary and IBM Position (long)
At 07:36 PM 2/18/2001 +0100, you wrote:
1.Primary output mode
(This affects the programmatic Portlet API)
Alternatives:
a) output stream as base mode in portlet package
sax as special mode in portlet.sax package
Thomas,
Excuse me for not being fully up to snuff...
At 10:25 AM 2/19/2001 +0100, you wrote:
Steve,
Suggestion: Add a configuration tag to the portlet definition
which specifies whether or not the portlet will produce partial
or full content.
You probably mean the deployment
,
Can you give an example of how such a stub should look like? You may indeed
have good ideas here...
Cheers,
Thomas B.
- Original Message -
From: "Steve Freeman" [EMAIL PROTECTED]
To: "JetSpeed" [EMAIL PROTECTED]
Sent: Sunday, February 18, 2001 21:32
Subject: Re: [vote] P
After the discussions we had during the last few days and
before the upcoming decision, I'd like to provide a new
summary of the current state of the discussion and explain
IBM's position in a separate section at the end, after the
dotted line.
We are all in agreement about our common goal :)
Thomas Schaeck wrote:
Unlike the Servlet API, the Portlet API would additionaly
provide explicit SAX support in the sax package and introduce a
dependency on org.xml.sax, i.e. a separate package. Such a
dependency of an API package to another API package that is not
part of the core Java
Sam Ruby wrote:
Thomas Schaeck wrote:
Unlike the Servlet API, the Portlet API would additionaly
provide explicit SAX support in the sax package and introduce a
dependency on org.xml.sax, i.e. a separate package. Such a
dependency of an API package to another API package that is
At 07:36 PM 2/18/2001 +0100, you wrote:
2.Fragments and/or Full Documents
(This affects portlet container performance and ease of
implementation - and thus development costs)
Alternatives:
a) only document fragments concatenatable without post-processing
- high-performance
