burtonator wrote:
>
> After creating the Jetspeed project and driving it to the point where it was
> about 8 months ago, I learned a LOT about what to do and what not to do when
> building a Jetspeed like application.
>
I know that time flies by, but you dropped of the project one year ago...
> I use the term "Jetspeed like application" because I believe the term Portal or
> Enterprise Information Portal has been used incorrectly. A lot of people have
> applied the term Portal to describe a client/server application which is behind
> a centralized web server.
>
> I do not believe this is the future of this technology.
>
> I believe the term Portal should be redefined to describe a fully distributed,
> XML centric, syndication framework with the addition of services such as
> Reputation, XML based content syndication, P2P style functionality (node-to-node
> caching, node-to-node syndication, HTTP layer which doesn't use DNS, etc),
> micropayment integration and language translation services. Privacy protection
> should also make up a significant portion of the project and it should support
> distributed, nym based authentication (which can drive reputation).
>
This is a nice and ambitious project, but this has nothing to do with current
Jetspeed goals :
We aim to create a portal engine, ie an application framework capable of
aggregating various applicative components into a single unified view and
provide the user with customization tools for selecting the content to
display and personalizing the content appearance.
Content Management is not something we're trying to solve because there are
already many projects tackling this issue from different perspectives (Slide,
Prowler, etc...) and as far as I can see, Reptile is just yet another with
buzzword P2P, XML and Privacy angle.
> They say a picture is worth a thousand words and I believe this describes the
> type of power this technology could give to the individual.
>
> http://relativity.yi.org/portal.png
>
Your host does not have DNS resolution.
> If you accept my redefinition of the term Portal it quickly becomes clear that
> Jetspeed won't solve these problems. The problem is that Jetspeed is a Java/Web
> application which uses XML in a limited manner. The correct interpretation
> should realize that XML is what is *most* important and that Java and any other
> specific technologies are used simply to optimize and transform XML.
>
This is completely bogus: Programming has always been the art of manipulating
and transforming data using deterministic algorithms. XML just introduces a
new standard and very flexible syntax for manipulating data. It does not change
in any way the need for processing data which can be expressed in any programming
language you care to use.
> Jetspeed could not function without the Portlet API. This is especially true
> because a lot of Jetspeed's own UI is generated with Portlets. Reptile handles
> this problem with Xalan extensions. This also has the added advantage of
> providing Reptile with a plugin architecture which supports other languages
> besides Java including Python, Javascript, etc due to the IBM Bean Scripting
> framework.
>
You mean you want to handle programming logic within XSL stylesheets ?
I think this is a dubious move at best, I'll stick to a manageable
programming language... Also, as you are very well aware, BSF is a Java package
which can be used to include scripting support in any Java application.
> Another main difference is that there is no PSML. Instead we use a system of
> layout, control and page schemas which can produce the same output but in a much
> more flexible manner.
>
Probably, a lot of systems are more flexible than PSML, the catch is to keep
enouch power while still offering user customization capabilities.
> Due this new design I believe that it is currently more advanced that Jetspeed.
> The main advantage that Jetspeed provides is that people are currently using it
> right now and it is stable. I would invite everyone here to take a look at
> Reptile and see what they think.
>
I think you have not looked at what Jetspeed provides recently and what is in
the works (new Portlet API). Reptile probably provides a more evolved
syndication system than the one currently provided by Jetspeed. I can easily
integrate this syndication engine into a Jetspeed portal if so I need, they
really tackle 2 different problems.
Also, you try to create from scratch an XML serving environment, you'd much
better integrate your specific features into Cocoon, with a couple of
transformers and generators you would have exactly the same functionality
but integrated in a solid, robust serving environment.
Why reinvent the wheel ?
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
