Re: GUI Handling of Modules

Some quick responses here. busy busy busy :-)

> In putting together the prototype Java interface for Apache I'm having

This has been disucussed as a wantlist item for 2.0 API changes. Something that would allow modules to register their presence and perhaps register for certain classes like Auth, Log, etc. _How_ to do this has never developed very far. It seems that the important information needed from a config interface point of view would be the Directives available. I'm not sure how one would pull this off pre-2.0 without making some guesses from the config files, or perhaps just the output of -h. Looking at the output of -h, that is probably your best bet.

> - once the configuration server is "module aware" you'll still need to

Tricky it would seem. It would be nice to keep auth options in the same interface instead of splitting them for each module.

> - finally, what's the best way to develop the configuration screens for

As mentioned, the -h info could give you a good starting point. It might be possible to create a module that would give you a hook more directly into this information so that you did not need to parse the output.

> What are your thoughts?

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek

I'm hoping to turn my attention about to this topic in the coming week. Received on Wed Jul 2 07:12:14 1997