From 8e2a05864ad5807a026967f1b9967189a4cf56b7 Mon Sep 17 00:00:00 2001 From: Andrzej Kapolka Date: Thu, 7 May 2009 02:22:25 +0000 Subject: [PATCH] Bring this maximum back down. I had thought that oversized datagrams were fragmented and reassembled at the network layer, but apparently that's not something one can count on. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@5770 542714f4-19e9-0310-aa3c-eee0fc999fb1 --- src/java/com/threerings/presents/client/Client.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/java/com/threerings/presents/client/Client.java b/src/java/com/threerings/presents/client/Client.java index 3e53bd2ec..dec446449 100644 --- a/src/java/com/threerings/presents/client/Client.java +++ b/src/java/com/threerings/presents/client/Client.java @@ -60,7 +60,7 @@ public class Client public static final int[] DEFAULT_DATAGRAM_PORTS = { }; /** The maximum size of a datagram. */ - public static final int MAX_DATAGRAM_SIZE = 8192; + public static final int MAX_DATAGRAM_SIZE = 1450; /** Our default maximum outgoing message rate in messages per second. */ public static final int DEFAULT_MSGS_PER_SECOND = 10;