I have a rails application on a remote server and a different rails
application on a local server. I need to exchange some data between
them. I have full control of both ends.
The Web Services chapter of AWDR begin with “This chapter is mildly
controversial…For new applications where you aren’t constrained by
external interfaces, you might want to consider using a lighter-weight
REST approach.”
Googling turns up a bunch of articles, but they tend to be older, and
I’m concerned that I wouldn’t be following the latest thinking. Any
pointers?
Thanks,
-George
George,
I have a rails application on a remote server and a different rails
application on a local server. I need to exchange some data between
them. I have full control of both ends.
The Web Services chapter of AWDR begin with …
WebServices are so 2006. ActiveResources is the way to go now.
Next to what you’ll find on the web, give a look at this page about
“internal mashups”.
RailsConf Europe: Hydra
The idea is to split one big monolithic app into many parts, running
on one or many servers.
Alain R.
On Nov 12, 2007, at 3:23 PM, Alain R. wrote:
WebServices are so 2006. ActiveResources is the way to go now.
Next to what you’ll find on the web, give a look at this page about
“internal mashups”.
http://blog.nicksieger.com/articles/2007/10/06/railsconf-europe-
hydra
The idea is to split one big monolithic app into many parts, running
on one or many servers.
Thanks Alain. Some interesting stuff there.