Does anybody use tg_format for anything other than setting up a URL
returns json?

We are thinking about depricating or dropping support for tg_format
becase we've come up with cleaner ways of doing content negotiation --
even for http get requests.

For requests where we can set the accepts header we can just use that.
  For URL based content negotiation we can use the extension.

If we did this /person.html would return HTML and /person.js would
return json (provided you've allowed that with an @expose decorator).
  Ideally, this would become extensible so that person.pdf could
return a pdf document if you had a buffet engine which could return
PDF.

What do you all think?

-- 
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to