specifying range for rmiregistry to bind from

Is there a way to limit the range of anonymous ports from which
rmiregistry picks for the redirect? We're paranoid enough we don't want
to simply open all anonymous ports to the entire subnet.

If we want to use just one port, it looks like UnicastRemoteObject( port )
should do the trick, if (according to the archives) one does not extend
the class.

For a range, it looks like the socket factory class is the place to look,
but I tried (once) and was unsatisfied with the results. (Couldn't get
it to run. Blame my lack of skill in Java.)

However, man rmiregistry indicates that the only options for rmiregistry are
for the port for the initial query and for passing options to java. So
it looks like I just have to figure out how to use or override the
socket factory class. Is that correct?

(I worry about all the things that RMIServerSocketFactory does and needs
done that I might not really understand, such as how to avoid ports that
are already in use by other processes when you don't just let the system
allocate the port, and why UnicastRemoteObject provides a constructor
which accepts separate factory instances for the client and server.
Incidentally, if anyone could point my to a page that shows IANA's
current definition of the anonymous port ranges, I'd appreciate it.)

--
Joel Rees   <[email protected]>
digitcom, inc.    $B3t<02q<R%G%8%3%` (B
Kobe, Japan   +81-78-672-8800
** <http://www.ddcom.co.jp> **

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html