Allow XHR timeout attribute to be overridden after send(), per spec

Source/platform/Timer.h

Index: Source/platform/Timer.h
diff --git a/Source/platform/Timer.h b/Source/platform/Timer.h
index 7c31c18912a61ab8fa3c7bb0bae5b5a7ffdacb4d..f5369e1d59e7a9fdd750c0018179c34353694ccf 100644
--- a/Source/platform/Timer.h
+++ b/Source/platform/Timer.h
@@ -45,6 +45,7 @@ public:
     virtual ~TimerBase();
 
     void start(double nextFireInterval, double repeatInterval, const TraceLocation&);
+    void startExact(double nextFireInterval, double repeatInterval, const TraceLocation& caller);

[Daniel Bratell, 2014/05/09 13:54:45]

As a user of this API I would wonder about the difference between start and
startExact.

Note that I'm not an owner of this code or the XHR code so my opinions are not
normative. :-)

 
     void startRepeating(double repeatInterval, const TraceLocation& caller)
     {
@@ -54,6 +55,10 @@ public:
     {
         start(interval, 0, caller);
     }
+    void startOneShotExact(double next, const TraceLocation& caller)
+    {
+        startExact(next, 0, caller);
+    }
 
     void stop();
     bool isActive() const;