Implement URLSearchParams.

Source/core/dom/DOMURLSearchParams.h

Index: Source/core/dom/DOMURLSearchParams.h
diff --git a/Source/core/dom/DOMURLSearchParams.h b/Source/core/dom/DOMURLSearchParams.h
new file mode 100644
index 0000000000000000000000000000000000000000..0196d8241200d6eccd99585f59e4ad78ee486515
--- /dev/null
+++ b/Source/core/dom/DOMURLSearchParams.h
@@ -0,0 +1,93 @@
+/*
+ * Copyright (c) 2014, Opera Software ASA. All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ *    notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ *    notice, this list of conditions and the following disclaimer in the
+ *    documentation and/or other materials provided with the distribution.
+ * 3. Neither the name of Opera Software ASA nor the names of its
+ *    contributors may be used to endorse or promote products derived
+ *    from this software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+ * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ * COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+ * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+ * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ * OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+
+#ifndef DOMURLSearchParams_h
+#define DOMURLSearchParams_h
+
+#include "bindings/v8/ScriptWrappable.h"
+#include "wtf/Forward.h"
+#include "wtf/PassRefPtr.h"
+#include "wtf/text/WTFString.h"
+#include <utility>
+
+namespace WebCore {
+
+class DOMURLUtils;
+class ExceptionState;
+
+class DOMURLSearchParams : public ScriptWrappable {
+public:
+    static PassRefPtr<DOMURLSearchParams> create(const String& queryString = String(), DOMURLUtils* urlObject = 0)
+    {
+        return adoptRef(new DOMURLSearchParams(queryString, urlObject));
+    }
+
+    static PassRefPtr<DOMURLSearchParams> create(DOMURLSearchParams* searchParams, DOMURLUtils* urlObject = 0)
+    {
+        return adoptRef(new DOMURLSearchParams(searchParams, urlObject));
+    }
+
+    String toString() const;
+
+    void appendNameValue(const String& name, const String& value);
+    void deleteAllWithName(const String&);
+    String getFirstValue(const String&) const;
+
+    Vector<String> getAllValues(const String&) const;
+    bool hasName(const String&) const;
+    void setNameValue(const String& name, const String& value);
+
+    void setInput(const String&);
+
+    void setURLObject(DOMURLUtils*);
+    DOMURLUtils* urlObject() const { return m_urlObject; }
+
+    void ref();
+    void deref();
+
+private:
+    DOMURLSearchParams(const String&, DOMURLUtils*);
+    DOMURLSearchParams(DOMURLSearchParams*, DOMURLUtils*);
+
+    void runUpdateSteps();
+
+    Vector<std::pair<String, String> > m_params;
+    DOMURLUtils* m_urlObject;
+    bool m_isUpdating;
+
+    // The object exists in two states: attached to a parent
+    // "URL object" or on its own if explicitly constructed from
+    // a script. Its lifetime needs to be managed by a ref count
+    // in the latter case.
+    int m_refCount;

[abarth-chromium, 2014/01/22 20:52:39]

Hum...  I didn't realize that it can exist in that state.  I'm not sure we want
to have two ways of managing a ref count on this object.  That seems overly
complicated.  Maybe we should wait until oilpan lands before implementing this
API.  I don't see a clean way of doing it given our current memory management
techniques.

+};
+
+} // namespace WebCore
+
+#endif // DOMURLSearchParams_h