Add web page replay to chrome_remote_control.

tools/chrome_remote_control/chrome_remote_control/page_runner.py

Index: tools/chrome_remote_control/chrome_remote_control/page_runner.py
diff --git a/tools/chrome_remote_control/chrome_remote_control/page_runner.py b/tools/chrome_remote_control/chrome_remote_control/page_runner.py
index 675f87d609b691fb25e2d360dbb580956045b319..cfd1e68f6548331f48aaba1358218f8f03b0a6f8 100644
--- a/tools/chrome_remote_control/chrome_remote_control/page_runner.py
+++ b/tools/chrome_remote_control/chrome_remote_control/page_runner.py
@@ -1,14 +1,17 @@
 # Copyright (c) 2012 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.
+import replay_server
 import os
 import time
 import urlparse
 
 class PageRunner(object):
-  def __init__(self, page_set):
+  def __init__(self, page_set, options):

[nduca, 2012/09/21 06:35:50]

I'm hoping once we allow the page runner to control browser startup, then we can
actually remove the --record options from the lower level primitives. Then, we
can make a record.py <pageset> that instantiates just a page runner without the
multi_page_benchmark and uses that to record the archive.

[tonyg, 2012/09/25 17:29:29]

Thinking about this more, record.py vs --record just means an extra script to
know about and some additional boiler plate code. What do you think about
keeping --record.

     self.page_set = page_set
     self._server = None
+    self._replay_server = replay_server.ReplayServer(page_set.archive_path,
+                                                     options.record)
 
   def __del__(self):
     self.Close()
@@ -17,6 +20,9 @@ class PageRunner(object):
     if self._server:
       self._server.Close()
       self._server = None
+    if self._replay_server:
+      self._replay_server.Close()
+      self._replay_server = None
 
   def PreparePage(self, page, tab):
     parsed_url = urlparse.urlparse(page.url)