I'm having a hard time thinking of use cases for this outside of zip or other archive/compression formats. In the case of user/1.xml.zip, likely you'd want an existing users_controller#show that returns xml to continue to operate as it currently does, but you'd want the result to be zipped. If there aren't lot (any?) of other situations where stack formatting is used, perhaps this would be better handled outside the scope of rails; let it keep doing what it's doing and maybe check the request URL for compression in rack on the way in and do the compression on the way out. If there are more general uses of this, it's still unlikely that you'd want a single controller action to handle both creating the xml and zipping it if necessary.
On Aug 4, 2012, at 1:56 PM, Alexey <[email protected]> wrote: > Also, there are request parameters, like sorting and filtering parameters, > which are common to all formats, so i would like all formats and downloads to > be processed by the same controller action. > > - Alexey. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-core/-/-ttQAFSi7NQJ. > 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. -- 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.
