What exactly is REST architecture and how is it implemented in Rails? -

It is that I think about the REST architecture.

For each resource, there is a unique URI

We can manipulate that object using its URI and HTTP actions [POST, GET, PUT and DELETE]. HTTP request represents the position of that object

I have read in all the texts, the rest have been explained in a strange and misleading way.

One more thing, implementation in the stable rail produces different URLs for different purposes. Like / teams -> 'index' method ... for teams / new-> 'new' method and so on. Is it not going away from the rest, which determines that each resource has a unique URI ???

I think your understanding of comfort is very good, it should be as much complex as it should be . Apart from this, @ sunya outlines some very good points.

The way HTTP methods are used for controlling methods according to the map:

  GET = & gt; PUT = & gt; Show Post = & gt; Update make DELETE = & gt; Delete  

Two other resources / methods that provide the railways:

  resource / new = & gt; New resource / editing = & gt; Edit  

Resources are not expected for all practical purposes but are necessary for the creation of web pages and applications, if the customer has complete knowledge of the resource, then they are not required. A customer can call only with POST and PUT resource information and can create and update resources as needed. But since users are not expected to know about these and other exclusions of a resource, they require an easy interface to work to create or update them.

If all the users are fully aware of the resources and were efficient enough to command line, we will not even need HTML, they will only be able to contact them with curl >

index makes it easy to work with the archive; it is still a well-defined resource and has a unique representation, for example < Code> / books> The Od How is controlled, does not make it Ristles (I made it yet, but it's amazing).