Hi,
I’m using RESTful in Rails, and I have an application with the
following situation:
I have categories, articles and comments. A category can contain many
articles (one-to-many relation) and an article can have many comments
(one-to-many relation). This is like nested in nested resources. My
question is how do I treat this in RESTful?
BTW, I’ve already implemented the code for categories and articles, I
still have to add the comments and I’m not sure how. If I add
comments, I’ll have to display the comments only inside the article
show view and there shouldn’t be a view where I can only see some
comments. Also, how do I integrate the comments_controller::index
action with the articles show view?
[email protected] wrote:
Hi,
I’m using RESTful in Rails, and I have an application with the
following situation:
I have categories, articles and comments. A category can contain many
articles (one-to-many relation) and an article can have many comments
(one-to-many relation). This is like nested in nested resources. My
question is how do I treat this in RESTful?
BTW, I’ve already implemented the code for categories and articles, I
still have to add the comments and I’m not sure how. If I add
comments, I’ll have to display the comments only inside the article
show view and there shouldn’t be a view where I can only see some
comments. Also, how do I integrate the comments_controller::index
action with the articles show view?
I would not think of an article as a nested resource within a category.
I think of a nested resource as something that is tied to the lifecycle
of the parent object. If you delete the parent, you also would want to
delete the children. In this case, article would be the parent and
comments would be the children because if you delete an article, you
want to delete the comments. In the case of something like a blogging
system, this would not be true of the category/article relationship and
so I would not use a nested pattern there.
mike
Hi, I recommend you to consult this paper by Google - “RESTful Rails
Development”
On the second part, it shows a pretty detailed example how nested
resource could be handled probably - how to revise route.rb, etc.
Hope this could resolve your puzzle.
Br,
Xi
On 10ÔÂ8ÈÕ, ÏÂÎç5ʱ21·Ö, “[email protected]” [email protected]
myst_tt, you forgot to post the link. thanks 
I’ve read this and I understand the RESTful concept. Though it’s not
obvious that I shouldn’t make the categories resources.