I’m building a client-server connection, which will target low bandwidth later.
At the moment I’m using sockets. But now I cam around RMI – which seems to provide my needs:
call a server-side method from the client-side.
My question is: should I go deeper to RMI, or are there even better approaches which I might not know about?
My goal is especially to have some methods on the server, which I then can execute by the client. So that my “message-queue” must not be static, as it has to be when just using socket and getting the strings from read().
I wouldn’t write such a thing from scratch.
RMI means a Java-only client and RMI or CORBA as a wire protocol.
Simple and open have won: why not consider an HTTP, web-based service exposing methods to clients via SOAP, REST, or RPC-XML? Those can be called by non-Java clients; they’re available on the web; they offer the same advantages as RMI.
I can’t see why anyone would start with raw RMI anymore. It’s lost the argument, just like CORBA did.