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 [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
