Mike, Kevin:
Just my 2c worth, but the approach we've been taking with our portal project
(which will integrate with Jetspeed) is very content-management oriented,
but it's not contradictory with Jetspeed's approach: The actual content (or
resources, as we call them) can be stored in any format, but the
meta-content, the information about the content, is either XML or in a DBMS
via JDBC. That way the content can be, as you say, very large, such as a
CDROM's worth of info stored in PDF format - the portal simply delivers it
(soon perhaps via portet mechanism :-) to the user(s).
For smaller content, such as news, calendar, etc, the data of the content
can be managed directly in XML.
Again, this is just how we're doing it, not the only approach I'm sure.
Mike
Javacorporate Ltd
http://www.javacorporate.com
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Cannon-Brookes
> Sent: Friday, February 18, 2000 11:04 PM
> To: JetSpeed
> Subject: RE: JetSpeed, Content and Persistence?
>
>
> Kevin A. Burton wrote:
> > Mike Cannon-Brookes wrote:
> > >
> > > G'day all,
> > >
> > > Great work with JetSpeed so far - I really like the Portlet
> > architecture.
> > >
> > > When I think of 'portal' I think of basically content
> > management system used
> > > by many users, with a host of 'applications' to access that content?
> > >
> > > I look through Jetspeed and I don't see any capability for
> > 'adding content'
> > > or persisting that content? For example news headlines,
> articles, press
> > > releases, events etc?
> >
> > Right. The content will be added via XML. Specifically it should be
> > defined by the user with an API for adding.
>
> Could you explain "added via XML" ? If a certain user group were
> allowed to
> add say 'headlines' to be displayed on the front page, they would be added
> through a web based form presumably? Then where would they go -
> straight to
> an XML file on disk somewhere?
>
> > > Is that the sort of thing JetSpeed is going to add? If so, how
> > will it be
> > > persisted? (EJB's? pure JDBC?)
> >
> > XML based on your Turbine username.
>
> What about content not tied to any particular user?
>
> What about 'large volumes' of content? XML is slooooow for storing and
> retrieving large volumes of content? (AFAIK It's not intended as a storage
> medium, more a communication and transfer medium for data?)
>
> Curious,
> Mike
>
>
>
> --
> --------------------------------------------------------------
> 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]
>
--
--------------------------------------------------------------
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]
