webservices status in rails

Discussion in 'Ruby' started by snacktime, Nov 20, 2006.

  1. snacktime

    snacktime Guest

    I heard rumors that webservices as they are now in rails was going to
    change or even be taken out altogether. Anyone know enough about it's
    future to say whether it's a smart idea to start basing a webservice
    on rails at this point?

    Chris
    snacktime, Nov 20, 2006
    #1
    1. Advertising

  2. snacktime

    Guest

    On Monday, November 20, 2006, at 02:41PM, "snacktime" <> wrote:
    >I heard rumors that webservices as they are now in rails was going to
    >change or even be taken out altogether. Anyone know enough about it's
    >future to say whether it's a smart idea to start basing a webservice
    >on rails at this point?


    The new REST support in the upcoming Rails 1.2 promises to make Rails one of the premiere platforms for building web services. Rails handles the server side beautifully. It assumes the data marshalling will be done with xml, but there's no reason it couldn't be extended to include SOAP envelopes.

    For the client side of the equation (and server-side too, to a certain extent) the new ActiveResource library looks incredible. I just started scratching at it this weekend and already I'm impressed. It does for web services what ActiveRecord does for database access; that is, it makes them brain-dead simple.

    So, avoid the ActionWebservice library unless you need to build something SOAPy "right now." Otherwise, look at Rails 1.2 and ActiveResource.

    cr
    , Nov 20, 2006
    #2
    1. Advertising

  3. snacktime

    Tom Copeland Guest

    On Tue, 2006-11-21 at 05:40 +0900, snacktime wrote:
    > I heard rumors that webservices as they are now in rails was going to
    > change or even be taken out altogether. Anyone know enough about it's
    > future to say whether it's a smart idea to start basing a webservice
    > on rails at this point?


    FWIW, I've got a server API (getindi.com) that's completely based on
    XML-RPC via actionwebservice. So actionwebservice will definitely
    continue in some sense or another, whether it's part of Rails core or
    not...

    Yours,

    tom
    Tom Copeland, Nov 20, 2006
    #3
  4. snacktime

    snacktime Guest

    On 11/20/06, Tom Copeland <> wrote:
    > On Tue, 2006-11-21 at 05:40 +0900, snacktime wrote:
    > > I heard rumors that webservices as they are now in rails was going to
    > > change or even be taken out altogether. Anyone know enough about it's
    > > future to say whether it's a smart idea to start basing a webservice
    > > on rails at this point?

    >
    > FWIW, I've got a server API (getindi.com) that's completely based on
    > XML-RPC via actionwebservice. So actionwebservice will definitely
    > continue in some sense or another, whether it's part of Rails core or
    > not...
    >
    > Yours,


    Thanks Tom! Good to know.
    snacktime, Nov 21, 2006
    #4
  5. snacktime

    snacktime Guest

    On 11/20/06, <> wrote:
    >
    > On Monday, November 20, 2006, at 02:41PM, "snacktime" <> wrote:
    > >I heard rumors that webservices as they are now in rails was going to
    > >change or even be taken out altogether. Anyone know enough about it's
    > >future to say whether it's a smart idea to start basing a webservice
    > >on rails at this point?

    >
    > The new REST support in the upcoming Rails 1.2 promises to make Rails one of the premiere platforms for building web services. Rails handles the server side beautifully. It assumes the data marshalling will be done with xml, but there's no reason it couldn't be extended to include SOAP envelopes.
    >
    > For the client side of the equation (and server-side too, to a certain extent) the new ActiveResource library looks incredible. I just started scratching at it this weekend and already I'm impressed. It does for web services what ActiveRecord does for database access; that is, it makes them brain-dead simple.
    >
    > So, avoid the ActionWebservice library unless you need to build something SOAPy "right now." Otherwise, look at Rails 1.2 and ActiveResource.


    The problem with REST is that it's not widely known, and most
    developers we work with are much more familiar with SOAP. Our job is
    to provide an api that the majority of our clients will be able to
    implement without the extra hassle of learning something like REST. A
    lot of our clients use .NET also, and the amount of extra work
    required to use a webservice that isn't SOAP based can be substantial.

    Chris
    snacktime, Nov 22, 2006
    #5
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. saha
    Replies:
    0
    Views:
    4,036
  2. Shug
    Replies:
    13
    Views:
    888
    Philipp
    Dec 15, 2006
  3. Replies:
    0
    Views:
    107
  4. Banaganapalle, Zafer [DAS]

    WebServices in Rails

    Banaganapalle, Zafer [DAS], Feb 12, 2009, in forum: Ruby
    Replies:
    1
    Views:
    99
    Luc Evers
    Feb 12, 2009
  5. kevid
    Replies:
    0
    Views:
    104
    kevid
    Oct 31, 2010
Loading...

Share This Page