> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Raphael Luta
> Sent: Thursday, August 31, 2000 8:00 PM
[snip]
> Mainly semantic. I view the Jetspeed system as using 3 kinds
> of non-engine
> related components :
> - viewers: basically takes a datasource and a set of
> parameters and produce
> output an output from this. RSSPortlet is a typical case.
> - datasources: these are data used to build the content, they
> must be uniquely
> referenced by an URL and may be defined externally (from a
> content feed
> for example). The FeeddDaemon currently builds a list of datasources (
> except that it's implemented as portlets definition in the registry)
> - producers: these components may be used to produce content based on
> a URL and request parameters. (typical producers would be HttpProducer
> to fetch URLs from the web, FileProducer to monitor local disk files,
> MailProducer...)
>
> The output of a producer is a datasource which can be
> displayed by a viewer.
> Actions on the viewer can trigger updates on a datasource by
> notifying the producer.
doesn't this start to overlap with Cocoon (espacially Cocoon2, actually)...?
Neeme
--
--------------------------------------------------------------
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]
