Are they necessarily mutually exclusive? Can X-JSON not stay for those who like it, and support for a _configurable_OR_standard_ content type be added? This seems like something that could be configurable at the application, page, or request level under various conditions or developer preference.
On 1/22/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote: > > On 1/22/07, Kjell Bublitz <[EMAIL PROTECTED]> wrote: > > > > > > But.. it's a matter of application design after all. Generally: mixing > > mime is bad. > > > Ever uploaded a file through a browser, or received a HTML/txt e-mail? I'm > sorry to break it to you like this, but you mixed mime when you did :) > > William F.: we got over the MIME-type discussion. "application/json" is > here to stay, "text/x-json" is invalid. > > Kjell, if I understand correctly, you're suggesting to drop X-JSON header > feature in favor of JSON in body? > > If we did that, it would make a lot of developers sad :( > > My reasons to keep it: > > 1. it's a simple hack; > 2. it's easy to do; > 3. it's not bloat to the framework; > 4. HTML, text or even XML with a side-dish of JSON is yummy. > > -- > Mislav > > > > -- Ryan Gahl Application Development Consultant Athena Group, Inc. Inquire: 1-920-955-1457 Blog: http://www.someElement.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
