http://bugzilla.novell.com/show_bug.cgi?id=552548
http://bugzilla.novell.com/show_bug.cgi?id=552548#c9
--- Comment #9 from Klaus Kämpf
Sorry, I did not have time to fix it until RC4.
There are at least two parts to this:
1) Prevent the restart of network. There are multiple levels where we could detect whether changes have been made: a) browser UI (Duncan suggested http://www.thoughtdelimited.org/dirtyFields/ ) b) web-client controller c) rest-service controller d) YaPI
The detection should take place at the earliest possible point. So a) is preferred.
2) What to do if the settings (IP address) really change. - we should warn about needing to reconnect (and possibly autorefresh to the changed address, if it is static).
Right, this is a usability requirement
- should we allow the IP address of a black box to be "randomly" changed via DHCP? Yes, but warn the user about the consequences. (This would apply only to a manual->automatic change.)
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.