Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Message-ID: <032901c1fda6$517c8cc0$12c68842@galina>
From: "Ivelin Ivanov" <ivelin@apache.org>
To: <forrest-dev@xml.apache.org>
References: <006f01c1fcd1$78be8200$670004c0@PC103>
Subject: Re: [] Dynamic system with WWH (what we have)
Date: Fri, 17 May 2002 08:25:31 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


I can only comment on the applet option.
If possible I would suggest that applets are avoided at this point.
Unfortunately they're not quite predictable on windows platform, especially
with all the mess MS intentionally creates. I can't run applets on my
Win98/IE 5.5 browser for a few months now.

However I would opt for pushing xml/xslt to the client, so that the real
time consuming operations are not performed on the server. By the time
forrest is ready for prime time, majority of browser installations will
support xslt.


----- Original Message -----
From: "Nicola Ken Barozzi" <nicolaken@apache.org>
To: <forrest-dev@xml.apache.org>
Sent: Thursday, May 16, 2002 7:00 AM
Subject: [] Dynamic system with WWH (what we have)


> [WARNING: Nicola Ken thinking out loud]
>
> It seems that when we talk about a dynamic system, we talk about online
> databases and servlets.
>
> Is this *really* necessary?
>
> Apache gives us these passive resources:
>
> - CVS
> - Bugzilla-Scarab
>
> Ant these active resource:
>
> - viewcvs
> - Gump
>
> The browser gives us these active resources:
>
> - applets
> - javascript
> - forms
>
> As you see, we have already more that a static website, and the last posts
> to Forrest and Cocoon have brought to these conclusions.
>
> Now, Forrest is a Community Tool, what others call a project/content
> management system.
>
> We need to
> - do the sites of the projects
> - do nagging-alerts
> - make stats.
> - recieve content updates
>
> The first three can be done ala Gump, what remains is the CMS we need, and
> what we have is CVS.
>
> To view content with CVS in real-time we could use viewcvs.
>
> Another option is to use an applet-Java app to get stuff from CVS and edit
> it.
>
> I think that this is the best solution, because it takes load from the
> server and can be made to run *now*.
>
> What do you think?
>
> --
> Nicola Ken Barozzi                   nicolaken@apache.org
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>