Moving Encoder and Decoder to remoting/base

Moving Encoder and Decoder to remoting/base

Putting Encder and Decoder together so we can have test that tests both
of them.

TEST=remoting_unittests

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=53427

[Alpha Left Google, 2010-07-15 19:47:08]

This is just a refactoring to move Encoder and Decoder to base.

This is necessary for writting test utils and routines that is reusable to test
encoder / decoder pair, which is what I'm going to do next.

[dmac, 2010-07-15 20:07:49]

LGTM

http://codereview.chromium.org/2840036/diff/3001/4006
File remoting/base/encoder_verbatim.cc (right):

http://codereview.chromium.org/2840036/diff/3001/4006#newcode26
remoting/base/encoder_verbatim.cc:26: if (EncodeRect(dirty_rect.x(),
dirty_rect.y(), dirty_rect.width(),
out of curiosity why split up the rectangle structure?

[Alpha Left Google, 2010-07-15 20:10:13]

http://codereview.chromium.org/2840036/diff/3001/4006
File remoting/base/encoder_verbatim.cc (right):

http://codereview.chromium.org/2840036/diff/3001/4006#newcode26
remoting/base/encoder_verbatim.cc:26: if (EncodeRect(dirty_rect.x(),
dirty_rect.y(), dirty_rect.width(),
On 2010/07/15 20:07:49, dmac wrote:
> out of curiosity why split up the rectangle structure?

Because in the header file I don't want to include gfx.