Yeah, but you guys should keep in mind that those cookies do come at a cost..Ie cookies still get sent around on each request...
I wish I had more time to play with it but I've been really curious what kind of "efficiencies" (however slight) might be had by making more use of other kinds of client side storage constructs.. Firefox 2 has a built in native type for it now, the other browsers can have the same thing through varying types of native objects. (usually flash / activex ) Either way they are all in Dojo and can be accessed through one single interface that allows you to not care what is happening and all should be very fast going from server->client && client->server. Now that I've got FireBug installed it's always worrisome when I see larger than normal cookie strings getting passed around. :) (maybe more worrisome in an ocd way than normal? ...) On 12/22/06, Kent Tong <[EMAIL PROTECTED]> wrote: <snipped>
> 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.
<snipped> -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
