http://gwt-code-reviews.appspot.com/1859804/diff/12001/user/src/com/google/gwt/user/client/Window.java
File user/src/com/google/gwt/user/client/Window.java (right):
http://gwt-code-reviews.appspot.com/1859804/diff/12001/user/src/com/google/gwt/user/client/Window.java#newcode223
user/src/com/goog
LGTM
http://gwt-code-reviews.appspot.com/1859804/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
LGTM
http://gwt-code-reviews.appspot.com/1859804/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On 2012/11/23 08:51:26, nfm wrote:
ping?
Sorry about that. It's hard to say which is faster without testing, but
I think having one cache is simpler than having two. So let's go ahead
with merging these variables.
http://gwt-code-reviews.appspot.com/1859804/
--
http://groups.google.com/group
http://gwt-code-reviews.appspot.com/1859804/diff/7001/user/src/com/google/gwt/user/client/Window.java
File user/src/com/google/gwt/user/client/Window.java (right):
http://gwt-code-reviews.appspot.com/1859804/diff/7001/user/src/com/google/gwt/user/client/Window.java#newcode322
user/src/com/google
On 2012/11/05 16:34:46, perneto wrote:
FYI: I added http://code.google.com/p/rietveld/issues/detail?id=402 to
track this change, as requested by Brian.
Oops, that's actually the rietveld issue tracker, not the GWT issue
tracker. The one you want is at:
http://code.google.com/p/google-web-toolki
You could also return a "Live" Map implementation so that the Map always
reflects the most up to date values even if getParameterMap() isn't
called. The same caching logic would apply.
On 2012/10/31 20:19:01, perneto wrote:
http://gwt-code-reviews.appspot.com/1859804/diff/1/user/src/com/google/
http://gwt-code-reviews.appspot.com/1859804/diff/1/user/src/com/google/gwt/user/client/Window.java
File user/src/com/google/gwt/user/client/Window.java (right):
http://gwt-code-reviews.appspot.com/1859804/diff/1/user/src/com/google/gwt/user/client/Window.java#newcode238
user/src/com/google/gwt/u
