accepts_nested_attributes_for vs. multiple controllers on one page

Hi,

I'd like to render the results from show, create, edit and delete actions for several different models (one controller per model) on one page.

While these several models are conceptually related, they do not need to be associated with each other. So, I'd rather not impose associations on them just to use accepts_nested_attributes_for to facilitate their presentation in a common form.

All I want is a page that presents the several models, links to their associated actions, and, finally, the results of these actions.

As a beginner, I'm having a hard-time fitting this requirement into the RESTful approach, where, as I understand it, each action is associated with at most one view.

Any comments?

Thanks,

Grar