On Mon, Jun 22, 2009 at 5:26 PM, Evan Adams <e...@google.com> wrote: > I considered this approach when responding in the bug report but ended up > rejecting it. > > The problem is that it "flattens" the query parameter space. Consider the > case where one of the query params is a continue url that has it's own > params. They will be encoded and this distinguishes the original-URI's > params from the continue-URI's params. If you decode the whole query string > that distinction is lost and you'll operate on the union of the two sets of > params. > > So, if the continue-URI also has a gwt.hosted param, then you won't be able > to distinguish the two. > > I think you need to break location.search into it's constituent params and > then decode each of them separately. >
But how do you break it down if you don't decode it? Since & is allowed to be encoded, that is ?a=b&c=d should be considered equivalent to ?a=b%26c=d, how can you know how to break it up if you don't decode it? -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
