Mike Orr wrote: > 1) Serve "/foo" as a container and let "/foo/" not exist, which is > what most Pylons apps do. > 2) Redirect "/foo" to "/foo/".
Either is fine (you can have a redirect for 1 too). The most important thing is just not to be ambiguous. And you should probably do redirects. > 3) Serve identical content for "/foo" and "/foo/". Not uncommon but VERY BAD. Don't even consider doing this. > 4) Serve different content for "/foo" and "/foo/". Uncommon BUT ALSO BAD. Zope 2, in a fit of cleverness, does this -- adding <base href> to one of those so the links work equivalently for either. It's a horrible awful thing. Resources and URLs should be one-to-one. Ambiguous URLs are one of those things in Zope that have scarred me, and seeing how hard that makes other things has made me sensitive to ambiguity elsewhere. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
