When it was time to write the choices.txt document, I had simply no valid justifications for using sockets and not rmi. In fact, my only justification was that sockets are faster and that I didn't want to learn rmi (speed is not a requirement for the certification).
I tried to use a custom port (other than 1099), it doesn't seems to work well... I'm thinking about always using the default port and not let the user choose it. What do you think?
Also, the certification document sais that rmi over http is not permited.
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog
Andrew:
It is very good to see that you have looked at your justification critically. There are other reasons why you might want to use Sockets (care to comment Phil ), but now that you have learnt RMI you can make a more valid judgement based on which one works best for you.
Yanick:
I feel much more confortable defending this choice [(RMI)] than sockets.
I start the registry in my code, while starting the server. (What is wrong with starting the registry in the program?)
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog