P4
Name: rmT116609 Date: 01/26/2003
A DESCRIPTION OF THE PROBLEM :
Make java.util.prefs.WindowsPreferences public or protected, we want access to the rest of the registry!!! We all understand why it's package authority, just as you understand why we want it public. Not much else needs to be said about that.
If you don't want the headache of supporting all these programmers using
java.util.prefs.WindowsPreferences for their own crap, then put it in
sun.util.prefs or something like that. That way you don't need to support
it. Plus, since WindowsPreferences wasn't a public class, you shouldn't
take any flak for changing the package name.
I haven't thought of all the security concerns, but I would think you could just have it throw security exceptions if it's outside of the sandbox.
The only real question is where to put the to do with the Base64 class if it's moved to sun.util.prefs...
(Review ID: 166259)
======================================================================
###@###.### 11/3/04 20:38 GMT
A DESCRIPTION OF THE PROBLEM :
Make java.util.prefs.WindowsPreferences public or protected, we want access to the rest of the registry!!! We all understand why it's package authority, just as you understand why we want it public. Not much else needs to be said about that.
If you don't want the headache of supporting all these programmers using
java.util.prefs.WindowsPreferences for their own crap, then put it in
sun.util.prefs or something like that. That way you don't need to support
it. Plus, since WindowsPreferences wasn't a public class, you shouldn't
take any flak for changing the package name.
I haven't thought of all the security concerns, but I would think you could just have it throw security exceptions if it's outside of the sandbox.
The only real question is where to put the to do with the Base64 class if it's moved to sun.util.prefs...
(Review ID: 166259)
======================================================================
###@###.### 11/3/04 20:38 GMT