Rich Roth wrote:
> > I was wondering if there is a written problem definition of what
> > a config gui should be able to do. I am surprised that there are so
>
> Actually there has never been one, each developer has taken his own attack
> at the problem. Part of what I am doing for the ApacheCon paper is a
> summary of all the ideas, approaches and tradeoffs in attacking the
> problem. I will post details (as I write them) for comment.
May I ask who's going to ApacheCon ? And who's presenting papers?
> > few around... particularly web based.... is there some reason for
> > this. finally I am fairly conversant in html as well as perl and I
> > think I could have haave a fair go at a web based configuration tool
> > but, I want to be sure that the idea of a web based config is sound
> > to begin with. Any thoughts.
>
> The issue of web based relates to how do you configure the web server you
> are changing, what if changes stop the server -- can the GUI be that
> trustworthy.. Also, what kind of security can be offered, simple password
> is probably not sufficient. The answer has been to have a mini-server as
> part of the UI tool. Even one written in perl would be an option.
>
> Also, a SSL type server is really needed to make the tool trustworthly, if
> it is used from remote sites -- which is pretty important.
I also thought of something like maybe a module to talk to from a config
tool
that would allow of changing the configuration of a *running* web
server,
although that is much less trivial to implement and would require to
specify
precisely the protocol used..
jb.
