On Tuesday, June 19, 2012 10:57:30 PM UTC+2, Arash wrote: > > Hi, > > I use "$" as the separator in my Tokenizer and then parse the token > respectively considering the "$" location. This used to work in gwt 2.3 > mainly because getHistoryToken(...) never returned "$" as part of > HistoryToken string. > In gwt 2.4 "$" character can be easily found in historyToken which > contradicts my assumption. The solution is simply switch to another > separator but I like to know what the contract is for historyToken encoding > characters so I can safely choose let's say "!" and be sure that > requestFactory.getHistoryToken(...) will never contain "!" >
IIRC, RF uses a Base64 encoded ID, except it uses chars $ and _ in place of the traditional + and /, and it uses an @ separator between ID parts. So ! should be "safe". -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/q1ajwDHyrCcJ. 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.
