Increase buffer size for XMPP sockets.

remoting/signaling/xmpp_signal_strategy.cc

Index: remoting/signaling/xmpp_signal_strategy.cc
diff --git a/remoting/signaling/xmpp_signal_strategy.cc b/remoting/signaling/xmpp_signal_strategy.cc
index 46f92943683df21a63bf1f0ff4a848d05504d26b..9b32a6362de82e6b6948da87abd3c086ff9de493 100644
--- a/remoting/signaling/xmpp_signal_strategy.cc
+++ b/remoting/signaling/xmpp_signal_strategy.cc
@@ -27,10 +27,16 @@ const char kDefaultResourceName[] = "chromoting";
 // connections that are idle for more than a minute.
 const int kKeepAliveIntervalSeconds = 50;
 
-// Read buffer size used by ChromeAsyncSocket for read and write buffers. Most
-// of XMPP messages are smaller than 4kB.
-const size_t kReadBufferSize = 4096;
-const size_t kWriteBufferSize = 4096;
+// Read buffer size used by ChromeAsyncSocket for read and write buffers.
+//
+// TODO(sergeyu): Currently jingle::ChromeAsyncSocket fails Write() when the
+// write buffer is full and talk::XmppClient just ignores the error. As result
+// chunks of data sent to the server are dropped (and they may not be full XMPP
+// stanzas). The problem needs to be fixed either in XmppClient on
+// ChromeAsyncSocket (e.g. ChromeAsyncSocket could close the connection when
+// buffer is full).
+const size_t kReadBufferSize = 64 * 1024;
+const size_t kWriteBufferSize = 64 * 1024;
 
 namespace remoting {