Moving Encoder and Decoder to remoting/base

remoting/client/plugin/pepper_view.h

 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This class is an implementation of the ChromotingView using Pepper devices
 // as the backing stores.  The public APIs to this class are thread-safe.
 // Calls will dispatch any interaction with the pepper API onto the pepper
 // main thread.
 //
 // TODO(ajwong): We need to better understand the threading semantics of this
 // class.  Currently, we're just going to always run everything on the pepper
 // main thread.  Is this smart?
 
 #ifndef REMOTING_CLIENT_PLUGIN_PEPPER_VIEW_H_
 #define REMOTING_CLIENT_PLUGIN_PEPPER_VIEW_H_
 
 #include "base/scoped_ptr.h"
 #include "base/task.h"
 #include "media/base/video_frame.h"
+#include "remoting/base/decoder.h"
 #include "remoting/client/chromoting_view.h"
-#include "remoting/client/decoder.h"
 #include "third_party/ppapi/cpp/device_context_2d.h"
 
 namespace remoting {
 
 class ChromotingPlugin;
 class Decoder;
 
 class PepperView : public ChromotingView {
  public:
   // Constructs a PepperView that draws to the |rendering_device|. The
@@ skipping 46 matching lines @@
   scoped_ptr<Decoder> decoder_;
 
   DISALLOW_COPY_AND_ASSIGN(PepperView);
 };
 
 }  // namespace remoting
 
 DISABLE_RUNNABLE_METHOD_REFCOUNT(remoting::PepperView);
 
 #endif  // REMOTING_CLIENT_PLUGIN_PEPPER_VIEW_H_