ActiveMessaging, ActiveResources or Ruby XMLRPC
I have a simple jruby + swt client that collects data on a randomly connected PC. Now I need to push these records to the server (Rails 2.3). Should I be using ActiveMessaging, ActiveResources or Ruby XMLRPC.
This is my real understanding:
-
ActiveMessaging is best when communication between server and client is required.
-
ActiveResources - hyper-opinionated client to CRUD server
-
RubyXMLRPC - Discontinued in Rails 2+. Flexible but adapts to poor design.
I would appreciate extra perspective, best practices, and quick and dirty.
Thank.
source to share
ActiveMessaging is designed to communicate asynchronously, so if you're looking for a server to send a message to say yes, I got this and processed it, you're out of luck. (I would know, I am a supporter of the project). Also, to send a message, you need to connect to a broker, and depending on firewalls, etc. This may not be possible.
There will most likely be some kind of http communication, and if you have structured or complex data to send, xml will make sense as the message format.
While cocky, REST and ActiveResource are well documented and supported, so why bother with it? This is what I would probably use, especially since you are using a Rails server.
As far as the xmlrpc is concerned, I believe your own comments provide a good reason to disqualify this option.
source to share