> When you're working strictly with Web browsers, 302 (redirect_to) is good > enough, or you can 200 (render). Not so for the programmable Web, which > makes a clear distinction between redirect and see other. Rails 2.0 is > tackling this sweet spot, with all the work around resources and > programmable data formats (XML, JSON), so it's certainly within scope. > > In fact, if you consider ActiveResource part of Rails, then the lack of > treatment for 303 is a bug. Have a look at ActiveResource to see how it > reacts to redirect_to following a POST. By that measure, we have an > expectation to 303 in the framework.
I dunno, there's a fine line between 'rest friendly' and 'worrying about impractical academic differences'. I'm not necessarily hugely opposed to adding a method, but the fact that it's only the two of us in this thread seems to say there's not a lot of appetite for this stuff. Anyone else have strong views on the matter? > In my opinion that's enough evidence for use to seriously consider how we > handle 303 in the framework. That's why I applied the patch for :status on redirect_to, I'm not denying it deserves thought, just that it doesn't need a method ;) After all, it's just a one line method in application.rb if you want it for now. def see_other(url) redirect_to url, :status=>:see_other end -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
