On 4 Apr 00, at 13:00, Kevin A. Burton wrote:
> So it is starting to come to my attention that there are certain hot
> spots that are within Jetspeed and aren't documented.
>
> - Adding users to Turbine (as well as general Turbine administration)
> - Authenticating users
> - What the individual packages do
I feel those 3 topics are the most important ones for starters.
> Just a break down of what needs to change before a major documentation
> effort should be done:
>
> - Adding users to Turbine (as well as general Turbine administration)
> - We need to work on a shared Turbine/Jetspeed admin console. I have
> a proposal drawn up I just haven't submitted it yet.
Just an idea of mine:
It might be easier to write an admin tool as a stand alone
application instead of a fully blown servlet/cocoon/Turbine/whatever
compliant version.
This way, a small tool might be generated which is useable for
easy administration tasks and acts as an example for others on
how the database itself is organized.
Later on, it might be converted to a bigger servlet based version.
Thoughts ?
> - Authenticating users
> - This area is one that needs work. We need to have an admin console
> (see above) and documentation on how to snap other
> authentication mechanisms in. Also user preferences haven't been
> integrated into Jetspeed yet and I would like to see this happen soon.
It might be worth considering the JAVA Authentication and
Authorization Service API JAAS introduced by SUN for pluggable
authentication services.
Though I have not heard anything about it since JAVAOne last year
and a quick search at the SUN page revealed nothing...
Anyhow, a pluggable architecture IMHO is the way to go here.
> - What the individual packages do
> - I plan on improving this in 1.2. Per package docs need to be done.
Great...
> - Where does the database/XML come into play.
> - This is still up in the air. There are a lot of technologies here
> that are competing :(. Ozone, Turbine, Castor, Quick, JXML, etc.
I expected this. Seems a lot of work has to be done :(
> - Management of the Persistent Document cache
> - Now the the Turbine scheduler is done this can be implemented to
> start when Jetspeed starts. It won't be a remote JVM process any more.
> Also there will be an admin console soon. (anyone want to write one?)
This is the viscious circle, at least for me:
If I knew enough about the JetSpeed architecture *and* had the
time, I�d do it.
But without this practice, I won�t be able to gain the experience
required ...
:-(
> So I hope this helps to make sense of things. IMO software needs to be
> evolutionary. Massive feature creep is one of the major evolutionary
> steps.
Absolutely agreed.
Keep up the good work.
Oliver
_______________________________________________________
S.E.S.A. Software und Systeme AG
[EMAIL PROTECTED] Dept. Stuttgart
http://www.sesa.de Oliver Fels
Tel. +49-711-139935-596 Mittlerer Pfad 2
Fax. +49-711-139935-510 D-70499 Stuttgart
_______________________________________________________
--
--------------------------------------------------------------
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]
