diff options
Diffstat (limited to 'guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/Platform.java')
| -rw-r--r-- | guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/Platform.java | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/Platform.java b/guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/Platform.java index 9497262f7..bb9fc16be 100644 --- a/guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/Platform.java +++ b/guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/Platform.java @@ -99,5 +99,16 @@ final class Platform { return exponent / 2; } + /* + * We will eventually disable GWT-RPC on the server side, but we'll leave it nominally enabled on + * the client side. There's little practical difference: If it's disabled on the server, it won't + * work. It's just a matter of how quickly it fails. I'm not sure if failing on the client would + * be better or not, but it's harder: GWT's System.getProperty reads from a different property + * list than Java's, so anyone who needs to reenable GWT-RPC in an emergency would have to figure + * out how to set both properties. It's easier to have to set only one, and it might as well be + * the Java property, since Guava already reads another Java property. + */ + static void checkGwtRpcEnabled() {} + private Platform() {} } |