All other things being equal, that is a reasonable decision to make . That is, if there is no specific reason to go for RMI or to go for Sockets, then going for the one you know best is a valid choice. However in order for you to be able to say that all other things are equal, you have to know what the pros and cons of each solution are.
I chose to use Sockets over RMI for the simple reason that i've never used RMI. Im guessing this is one if those major design decisions I might be asked to talk about in the exam or in the choices.txt file, but of course I can't say that i chose to use Sockets just because I don't know how to use RMI.
I can tell you lots of reasons - in the book we wrote over 4 pages comparing and contrasting the two technologies. Might be a bit too much to be posting here though.
Could you tell me of any good reasons why choosing Sockets would be better than using RMI?
Get meta with me! What pursues us is our own obsessions! But not this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton