I like the ability to enable or disable http/https transports in the UI. There are a few user model questions that arise from it though:
1) What does it mean to disable both http and https transports? Do we want to prevent this? (allow only http, https, or both) 2) Disabling transports seems conceptually similar to starting/stopping the service. Yet one is listed under "Management Tasks" and one isn't. Although configuring transports sounds like a "Management Task" that panel is already getting pretty complex and I do like the more verbose style in place currently. Maybe we need to separate configuration tasks from management tasks? 3) When you're not an admin or the author, you don't see the transport information, which could be useful. I also now notice that unless you're the author or admin, you can't see whether the service has been started or stopped. As a user I think this information could be critical. Maybe we can display it always but only allow changes by the admin or author. For start/stop, this again supports moving this information out of the "Management Tasks" panel since it wouldn't represent a "task" at times - just configuration information, and thus would look a little out-of-place in a task panel. What do you think? Jonathan Marsh - <http://www.wso2.com> http://www.wso2.com - <http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com
_______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
