> > The thing is, if people start adding extra configuration modules > (Mailets and Matchers, for example, may add config options) then the > tree view works better, and can speed up navigation than if the nav > options were just available in a top nav bar. >
I was thinking about extensibility also and trying to go for something along the lines of Plesk which you mentioned. The idea was to put the actual options with icons in the body of the page, that way you can have any amount of them, as seen here: http://www.sw-soft.com/r/upload/screenshot-plesk75reloaded_domain_violet-495x371.gif The problem i have with the tree view is that its concept serves the purpose of being able to switch between leaves in different branches or have a total overall view of the tree, which might not be that important here. Each section in the prototype already includes about 15 to 20 items, so a fully expanded tree with all of them (plus additional ones as you mention) could turn into a pretty large list, which might not be too friendly. I was hoping we could get icons like in the plesk interface to make the identification of options a fast / easy thing. I was also thinking about making it the easiest possible job for new developer who have not worked on the console before to add new functionality to it. What do you think? > The only real issue is the problem Jason mentioned about JMX security, > and I'm equally encouraged by the quick fix he also came up with: > having JMX bind only to localhost. However, the tiny problem with that > is, what happens when James is on one server and the admin console is > on another server? Do we just require both to be on the same server? > Also, what about clustering? Will we have to run a James Admin console > for each clustered box, or can we address just one controller box? This problem is the reason why i pointed out the possibility of using the MX4J based SOAP connector. This would allow us to use ws security or basic http authentication to secure the JMX access and work in network mode. Juan Carlos Murillo <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
