> -----Original Message-----
> From: Raphael Luta [mailto:[EMAIL PROTECTED]]
> Sent: Dienstag, 7. November 2000 06:20
> To: JetSpeed
> Subject: Re: Portlet API
>
>
> [EMAIL PROTECTED] wrote:
.....
>
> > For handling the second scenario, complicated mechanisms
> for rewriting,
> > handling of cookies and probably other issues may be built into the
> > portal implementation, but they should not impact the portlet API.
> >
>
> I even think such capabilities should be handled by the portlet itself
> just like the AdvancedFilePortlet presented. There will never
> be a proper
> way to aggregate different legacy documents in a single page.
>
I disagree, because especially if you want to take care about namespaces,
prefixes for variables/javascript functions, cookies and so on, this
should be places inside of the framework, because only the framework knows
each source inside of an page and can check inter-dependencies. Some other
stuff like changing relative to absolute URLs can be inside of the portlet.
In our case this was just an easy and quick way to enable this
functionality.
>From an architectural perspective I would preffer to have some parts of this
functionality inside of the framework.
Marcus
--
--------------------------------------------------------------
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]
