Simplify BufferedSocketWriter by making it non-thread-safe.
Originally BufferedSocketWriter was implemented to be thread-safe,
so that any thread can call Write() method. We don't write any data from
other threads anymore, so there is no need to keep it thread-safe.
Review URL: https://chromiumcodereview.appspot.com/10411082
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138694 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/remoting/protocol/client_event_dispatcher.h b/remoting/protocol/client_event_dispatcher.h
index 0b694014..ab742f25 100644
--- a/remoting/protocol/client_event_dispatcher.h
+++ b/remoting/protocol/client_event_dispatcher.h
@@ -6,14 +6,13 @@
#define REMOTING_PROTOCOL_CLIENT_EVENT_DISPATCHER_H_
#include "base/memory/ref_counted.h"
+#include "remoting/protocol/buffered_socket_writer.h"
#include "remoting/protocol/channel_dispatcher_base.h"
#include "remoting/protocol/input_stub.h"
namespace remoting {
namespace protocol {
-class BufferedSocketWriter;
-
// ClientEventDispatcher manages the event channel on the client
// side. It implements InputStub for outgoing input messages.
class ClientEventDispatcher : public ChannelDispatcherBase, public InputStub {
@@ -30,7 +29,7 @@
virtual void OnInitialized() OVERRIDE;
private:
- scoped_refptr<BufferedSocketWriter> writer_;
+ BufferedSocketWriter writer_;
DISALLOW_COPY_AND_ASSIGN(ClientEventDispatcher);
};
