Howard Lewis Ship <hlship <at> gmail.com> writes: > I feel the cookie should outlive the session, so that when people return to > the site at a later date, they can view the site in the appropriate locale. > I thnk of it as a kind of "bootstrapping" property.
I see. > The alternative would be to build the locale into the URL. The problem with > that is that once I add in support for templates in the context, I'll want > to be able to support relative paths to assets. If the locale is in the > path, that will break it (the template will be at /Start.html, but the base > URL for rendering the page will be something like /en/Start.html, and a > relative asset, such as src="images/logo.gif" will evaulate to > "/en/images/logo.gif" and break). I think this will also go against the principle of that a URL should represent a resource, not a particular presentation of a resource. > Oops; just remembered, because of passivate/activate, relative URLs will > already be broken. I.e., a typical path may be > "/admin/DisplayUser.html/1234". Possible to let the PageRenderDispatcher sets the Content-Location HTTP header to /admin/DisplayUser.html? -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
