抄自
In essence, routing resources is when resources gives action abilities to a controller.
If a pluralized resources is used as a way to handle generic requests on any item, then a singular resource is a way to work on the current item at hand.
So in other words, if I have a collection of Apples, to retrieve a specific apple, I'd have to tell the router "Apples" what apple to retrieve by sending the ID of the apple. If I already have one Apple, then an ID is not needed.
Notice the differences between the two by looking at what actions (or routes) they have:
- resources: Index, new, create, show, edit, update, destroy
- resource: new, create, show, edit, update, destroy
In your example:
- The controller "geocoder" is a singular resource that you can use to edit, create, update, etc.
- The controller "posts", is a plural resource that will handle incoming generic posts that you can index, edit, create.. etc
简单的说，resources比resource多了个index方法，针对具体业务的时候，resources适用于复数资源，resource用于单数资源