RMISecurityManager vs SecurityManager

According to the Java API documentation ,

RMISecurityManager implements a policy that is no different from the policy implemented by SecurityManager. Therefore, the RMI application must use the SecurityManager class or another SecurityManager implementation for the application instead of this class.

If so, what is the point of having a separate RMISecurityManager class? Are there any situations where they should be used over the SecurityManager?

+3
source share
1 answer

It makes no sense. If you look at the definition of RMISecurityManager:

public class RMISecurityManager extends SecurityManager {

    /**
     * Constructs a new <code>RMISecurityManager</code>.
     * @since JDK1.1
     */
    public RMISecurityManager() {
    }
}

. , . , .

+2

Source: https://habr.com/ru/post/1776309/


All Articles