This is more of a design principles question. Would you put *all* the information needed to render a page in the URL? For example, I've extended user_table to store some extra information we need, and the contents of pages depends on those values. Visitor 'foo' and visitor 'bar' would see completely different values when requesting "/reports/something", which uses identity.current.user.customfield to determine what to show.
This code is basically a re-write of a Zope application where this made sense, but I'm not sure if that's a good idea for new development. Pros: state information is hidden, so users don't see ugly URLs like "/reports/something/valueofcustomfield". Also, I don't have to add that argument to methods because it can be retrieved from inside those methods. Cons: state information is hidden, so caching has to know about internal state of methods and you can't always assume that "/reports/something" will return the same thing for all visitors. So how do you handle this? I don't see one as clearly better than the other and I could use the voice of experience here. -- Kirk Strauser --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
