All interfaces and classes can be used locally as well. This allows to hide the distinction between local and remote access throughout the application.
The availability of the remote access to a running simulation is provided through the class {@link de.renew.remote.RemoteExtension}. A default server implementation is provided by {@link de.renew.remote.ServerImpl}.Used properties | |||
de.renew.remote.enable | boolelan | false | Controls whether the remote access to local simulations should be allowed or not. |
de.renew.remote.publicName | String | (not set) | Specifies the name part of the URL under which the
remote server will be announced at the RMI registry.
If not set, the
{@link de.renew.remote.Server#DEFAULT_SERVER_NAME default name}
will be used. |
de.renew.remote.serverClass | class name | (not set) | Specifies a custom {@link de.renew.remote.Server}
implementation to use. If not set, the default
{@link de.renew.remote.ServerImpl} is used. |
de.renew.remote.socketFactory | class name | (not set) | Specifies a custom {@link java.rmi.server.RMISocketFactory} implementation to use. If not set, the default RMI socket factory is used. |