You cant actualy change the url parameters like you can the history,
because changing them would refresh the page.
google.com#?blah=blah   would be a history token that just pretends to
be a normal parameter. (and  Window.Location.getParameter wouldnt work
for it).
This can be changed without a page refresh

Any change before a #, however (such as google.com?blah=blah) would
cause a page refresh, and thus cant be done with a continuously
running app.

This cause's much announce in combination with the fact severs cant
access "#", as it makes it very hard to give your users url's which
both always link to the same data, and work for clients without
javascript. (such as google bots)


On Jul 16, 5:46 pm, KevMo <[email protected]> wrote:
> Thanks Max,
>
> I did find that post earlier, however since there is a built in way of
> getting URL parameters I thought there would also be a built in way of
> setting them.  That post suggests using the history to set the
> parameters, but then I would need to make my own functions to parse
> the history token for the parameters.
>
> Cheers,
> Kevin
>
> On Jul 15, 9:24 pm, Max <[email protected]> wrote:
>
>
>
> > Hi KevMo,
>
> > I think you can find this information in this 
> > post:http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa...
>
> > Also you can search for "URL Parameters" or "Parameters" in this group
> > so find more posts.
>
> > Regards,
>
> > Max
>
> > On Jul 15, 11:00 am, KevMo <[email protected]> wrote:
>
> > > I know I can getURLparametersby using Window.Location.getParameter
> > > (), but how does one programatically set theurlparameter?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" 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/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to