cfis : Making Rails Better - Content Negotiation

Comment on Making Rails Better - Content Negotiation by Jim Cropcho

Mon, 06 Aug 2007 16:00:22 -0600

Charlie,

Looks interesting! I passed this on to a developer who’s working on a project with respond_to for FindHolmes.

Comment on Making Rails Better - Content Negotiation by dstar

Tue, 07 Aug 2007 08:38:57 -0600

The second problem is that the implementation mixes view logic into a controller. Why should a controller have knowledge, or care, about how its results are rendered? I can’t see any good reason for it.

Isn’t the controller responsible for selecting the view to be used? At least, that’s my understanding of MVC, and from that perspective, the respond_to code seems perfectly reasonable, since the different formats are effectively different views (this does, of course, assume that the only change is the template used, and not the actual data returned)

I won’t, of course, try to defend the necessity of boilerplate code. That’s just wrong.

Comment on Making Rails Better - Content Negotiation by Charlie

Tue, 07 Aug 2007 11:43:40 -0600

Hi dstar,

Yes and no - the logic for selecting a view is split between ActionController and ActionView. On the controller side you specify a template or file and then the view side analyzes the existing templates and their extensions and picks the right one.

To fit into Rails as it is, the plugin doesn’t change the division of logic.

Comment on Making Rails Better - Content Negotiation by Nicolás Sanguinetti

Wed, 08 Aug 2007 23:35:19 -0600

This seems to be great, I will totally play with this as soon as I get back to doing some rails work :)

AFAIK, for what I’ve been doing with edge, even if the core team is thinking on going this direction, it currently doesn’t work this way, you still have to write the respond_to blocks, though I might be completely wrong.