Hi Marcos,
(you really read all of these messages! amazing)
Sad isn't it?
[Andrew] may not be possible to use external RMI Registry
[Marcos] why? anything related to security policy?
I was thinking more of the way most people start the registry programattically, and just exit the program if they cannot start their own registry.
But since we are talking about security, there is another potential problem with people starting their own registries. If you don't have a security manager, then no other application can bind to your registry. This is something you probably only want to make a note of, because we don't really want to be adding a fully fledged security manager to our application. But if we don't allow the port number to be changed, we don't attempt to bind to an already running registry, and we don't allow anyone else to bind to our registry
[Andrew] since stubs are local to client, if ever you change server side, you will have to provide clients with new stubs (rather than the client dynamically downloading them as required).
[Marcos] This is because the client is tied to a specific remote interface but the server can use different implementing classes and the client will download them as needed?
Yes. Or even the server changes something minor which results in a new version of the stub being generated with a different serialVersionUID, so the existing stubs no longer work.
Regards, Andrew