Best practices for develop a web service (server+client)?


#1

Hi, i’ve two applications (APP1 and APP2) and i want that APP2 is able
to get data from APP1. I think that a simple rest web service is the way
to go. Do you have some good examples/tutorials? I’ve googled but i find
only old examples with the deprecated action web service. From the
client, who get the xml, how does reconvert it into ruby/model objects?


#2

What about activeResource ?

On Jan 28, 11:02 am, Xdmx X. removed_email_address@domain.invalid


#3

Xdmx X. wrote:

Hi, i’ve two applications (APP1 and APP2) and i want that APP2 is able
to get data from APP1. I think that a simple rest web service is the way
to go. Do you have some good examples/tutorials? I’ve googled but i find
only old examples with the deprecated action web service. From the
client, who get the xml, how does reconvert it into ruby/model objects?

If the apps aren’t rails specific, I would suggest to write a simple
rack application. It’s actually pretty useful when interfacing API’s
that are non-rails.


#4

remotely related …

Can Rails on Ruby work with an established sqlite3 (or mySQL) database?
the tutorials I have read so far build the sqlite3 tables with the $
"ruby script/generate model … " command.

I guess what I am trying to figure out is if the Ruby R. platform
will be a wise investment of my time to learn and eventually become
proficient if my goal is to build some web applications that interact to
already established databases.

I would prefer to build my database the old fashioned way - e.g., SQL
CREATE statements - and be able to modify the structure on the fly
(structure and data). The web pages would be a simple GUI interface for
my computer challenged friends! :slight_smile:
I am hopeful that the Rails on Ruby will allow that flexibility?
Eventually, I suspect that I will be good enough to do it all in Rails
like you all do.

Advice?

thanks in advance


#5

Freddy A. wrote:

What about activeResource ?

You mean activeresource for the rest approach ? for that sure, but you’d
always have the client who request a given url and get some xml to
parse… right?

Which is the better format to give the client between xml and json ?
And how to parse back from xml/json to a an object to include in the db?
Just a simple loop over all the data and a Model.create(…) for
each?

Nate L. wrote:

If the apps aren’t rails specific, I would suggest to write a simple
rack application. It’s actually pretty useful when interfacing API’s
that are non-rails.

both are rails apps


#6

Yeah rails is fine to do this stuff in. We use migrations because thy
make structure maintenance easier especially if your app is deployed
in multiple locations (or even just across a deployment an a
development machine)

Sent from my iPhone

On 29/01/2009, at 4:11 PM, Jay Mcgratgh
<removed_email_address@domain.invalid