On Aug 4, 2006, at 9:22 AM, Michele Cella wrote: > > Kevin Dangoor wrote: >> >> Actually, @view/expose already handles multiple types of responses >> (not based on HTTP method but based on accept headers and tg_format). >> > > Yes, I know that that's why it makes sense to call it @respond IMHO. > ;-) > > Anyway that's not a big problem just another idea to throw into the > discussion.
The reason I'm more keen on @view is just that that is existing terminology (and TG is based on the model/view/controller pattern). I think the only case where the metaphor feels stretched is the method that redirects case, so I'm going to go with the decent number of +1s on this and add @view. (As I said originally, there will be no backwards compatibility issues or deprecation warnings for this change.) Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
