I think that moving to a swing based console at this point in time would
be the wrong move. As Chris and Paul have mentioned, Ajax and other
technologies are moving toward closing the function/usability gap for
web based applications. A web based console provides greater
flexibility for administration from various device types in the future.
And rich clients introduce another whole set of client issues that
we then have to consider. Technologies like JWS do help with the
install/mgmt of the clients but don't address other client side issues
such as verification on multiple (sometimes obscure) platforms, JRE
versions on the client, hardware requirements, etc...
I agree with the exposure that Heinz has pointed out of running the
admin console on the same platform that it is managing. However I think
we need to view the admin console within the complete context of
Geronimo. The console is a great usability enhancement in managing
Geronimo and for most users is the primary way that they will manage
Geronimo. However, it is not (and should not) be the only management
tool. Anything that is possible with the web console should also be
possible (but not necessarily as easy) via some some other means.
It would be good if we could insulate the console further from the
server (possibly running it on it's own minimal configuration as Greg
mentioned) but we need to consider the server cost/benefit trade-off any
such choices.
Joe
Heinz Drews wrote:
Chris,
I agree that with Ajax sufficient functionality can be provided in a
webapp.
My primary argument for a rich client would be as I have said before
that a webapp requires a running server. And what should be done if
there are problems in the configuration which prevents that the server
starts?
The console webapp should at least run in a seperate server with
minimalistic configuration.
Something which I would prefer anyhow instead of the current situation
in G.
Heinz
On 9/19/06, Christopher M. Cardona <[EMAIL PROTECTED]> wrote:
I think this idea can be explored but we should give the current
initiative to include Ajax functionality to the console a shot first.
There's no doubt that rich clients have their advantages over web apps
(performance and sophisticated widgets to name a few) but I think we
have a potential in Ajax to close this gap. It would be nice to get more
comments on this. What do others think?
Jason Dillon wrote:
> Anyone have any thoughts on using Swing for the console... instead of
> a webapp (which are kinda evil IMO)... and then using webstart to
> serve it? Maybe using Netbeans (or that license not ASL friendly)?
> I've done some work with NB before at it would be very easy to create
> a rich user experience... and its easy to drop in new modules to
> support different aspects of administration and monitoring.
>
> I dunno.. just a thought...
>
> --jason
>
