> we would need to create some kind of redirection between # and not # urls if > users want to share urls.
That's the problem. The # and everything after it are not sent to the server. It's only on the browser. So you can't redirect based on the octothorpe. The only way to do things then would be to give everyone the "domain.TLD/blah" URL and then forward those to a "domain.TLD#blah" if you've detected that they don't support pushState. However, that's best done in JS (or you'd need an exhaustive list of user agents and pushState support). So, if you could make all "domain.TLD/" requests forward to your index page, while keeping the URL, then bootstrap some pushState detection logic, and then redirect to the othothorpe version (build permutation) if they don't support push state, you might be able to swing it. Should be possible, but obviously complex and why the othothorpe remains standard. Joe -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
