On Wed, Apr 16, 2014 at 8:55 AM, Robert Walker <li...@ruby-forum.com> wrote: > Colin Law wrote in post #1143272: >> On 16 April 2014 13:34, prabhu <pradeep.achut...@gmail.com> wrote: >>> Hi, >>> >>> I am trying to create a Rest web service in my rails application. I need to >>> configure urls for it as below. >>> >>> >>> localhost:3000/book/book_id/new/param1/param2/param3/param4/... >> >> That might be better as book/id/new?param1=..¶m2=.. etc. >> What is that url supposed to do? If it makes a new book then why have >> you got an id? > > As Colin noted, if this is intended to create a new book then it seems > more logical to me to send this as a POST with the parameters in the > body of the request (either supplied as form data or JSON) and not in > the GET style of appending the parameters to the URI.
One should not accept JSON input outside of a API interface built with REST semantics because then you are just muddying the waters and enforcing multiple types for something that is probably purely for HTML and doesn't even need a secondary type. It's a bad idea to combine your API REST and REST interfaces for HTML into the same endpoints. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAM5XQnzaHkespzKfuDZLZziYX-sybgNR5Pww1o8xAMqS3EzZRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
