[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jetspeed-user
Subject:    RE: PORTLET SERVERS ???
From:       "David Sean Taylor" <david () bluesunrise ! com>
Date:       2001-06-28 21:32:36
[Download RAW message or body]

> (which by the way is pretty slick in itself).  Another
> rip-off idea I had by
> examing their architecture is their strategy for handling external
> applications.  I noticed that the Jetspeed applications
> portlet was disabled
> (probably due to the complexity involved in implementing this
> functionallity; cookies, URL rewriting, etc.).  It seems that
> the Plumtree

You want to look at the cvs head for a portlet named WebPagePortlet.
(This portlet is not distributed with 1.3a1)
The WebPagePortlet does basic URL rewriting and tag filtering.
It also needs to handle post parameters, session management (cookies),
script naming resolution.
I will update the portlet with post parameter and session management support
in the near future.
The scripting issues are rather complicated. We had some discussions on this
subject on the mailing list back around october or november

-------------------------------------
David Sean Taylor
taylor@apache.org
-------------------------------------
http://jakarta.apache.org/jetspeed
-------------------------------------




> -----Original Message-----
> From: Frank Villarreal [mailto:fvillarreal@directhitdata.com]
> Sent: Thursday, June 28, 2001 1:03 PM
> To: jetspeed-user@jakarta.apache.org
> Subject: PORTLET SERVERS ???
>
>
> Dear Jetspeed Developers:
>
> I've been examining the Jetspeed 1.3a1 code build for several
> months now.
> <compliment>I've been highly impressed with the progress of
> this project
> thus far. Hats off guys.</compliment> However, there is so much more
> untapped potential functionallity.  Just as food for thought,
> what about
> creating standalone portlet servers for external sites.  In
> other words, a
> Jetspeed component that serves content and itself is hosted
> by an external
> server.  I saw this technique being used by the Plumtree
> portal architecture
> (which by the way is pretty slick in itself).  Another
> rip-off idea I had by
> examing their architecture is their strategy for handling external
> applications.  I noticed that the Jetspeed applications
> portlet was disabled
> (probably due to the complexity involved in implementing this
> functionallity; cookies, URL rewriting, etc.).  It seems that
> the Plumtree
> architecture defines a more rigid separation between the
> portal and portlets
> (they live on different physical servers) and use propietary
> data embedded
> within the HTTP headers to communicate. I haven't looked at
> the latest CVS
> head, but is any of this functionallity planned or even
> desired for future
> releases of Jetspeed?  Comments, rants, ideas?
>
> Frank T. Villarreal, Jr.
> Director, Information Systems
> Direct Hit Data, Inc.
> Email fvillarreal@directhitdata.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]