Rajesh Thiharie wrote:
> +1.
> This should be very beneficial for anyone who wants to pump content
> different ways.
>
> Santiago Gala wrote:
<cut the message>
The idea comes when you look at Jetspeed. Essentially, the look of jetspeed is the one
of a
windowing system (like Xwindows or Windoze). If you carry the analogy further, we get
(along the
lines of your previous messages):
- Basic OS services (servlet engine, turbine, jyve, ...) Things like pools of
resources,
authentication, session separation, etc, are solved here
- Graphic drivers (Jetspeed is partially here, with a lot of help from Cocoon, our
HPGL for XML)
- Interface widgets. Jetspeed defines some of these. More are missing, like
abstractions for
drop, combos, etc.
- Event registration, dispatching, delegation... (I think from this area down a lot of
work is
needed)
- Action definition and delegation (for instance for validation, or for downloading
process to
the client)
On the other side, Jetspeed is ALSO a tool for selecting and viewing information
channels. What
I mean is that there are two separate functions here. This second function is
interesting, I
like it a lot. But I think we need both things. It we had a framework like the one we
speak
about, I think this second Jetspeed would be fairly easy to write, as a service on top
of it.
We are missing the concept of application/service. The example is: I would like to
write a
Webmail, that could run in a different machine, and specify the different portlets
that it would
have (icon for messages pending, folder list, compose window, inbox, ...) and the
framework
would map the application events I would specify to requests to my app/service and
control the
layout and rendering separating the Media, Desktop and user issues from the
application design.
This would enable a Model-View-Controller, where a Portlet is a view, a service
provides a
model, and the controller would be specified on top of jetspeed/turbine to map the
events and
control interaction. Something similar to a multi-window application under X. X moves
the
events, the windows are views on the data, and the application itself is the model for
the whole
thing.
I don't know turbine well enough, but I think it provides funcitonalities around these
lines.
Last tuesday Ricardo Rocha showed me an example of a vocabulary used to express forms
in XML.
Something simple, but there was an interesting issue. He said that a field would be
upper case,
and then he coded, via stylesheet, that in netscape and explorer this would be
executed with
javascript in the browser. This brought up the issue that we need to specify if an
event can be
delegated to the media, or else executed in the application. Some media will not give
us
"hardware support" for things like these. This brings the issue on how to express
actions in a
way that can be mapped to different media or executed in the server
This would be our "Windows.net" network operating system, the way that we could
separate
applications, desktop and devices in web development. So now the browser is a display,
the web
server is the desktop for the user and the client for an application server that will
interact
with it.
In any case, I think we are speaking here Jetspeed 2.0. I think a discussion on who
will manage
the different functions (Turbine, Cocoon, Jetspeed, other approaches like Enhydra,
...) is
needed.
For Jetspeed 1.2 it is better to have something working out as soon as possible.
Regards,
Santiago
--
--------------------------------------------------------------
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]
